Internet Protocol flow information export: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>Howard C. Berkowitz
No edit summary
mNo edit summary
 
(2 intermediate revisions by 2 users not shown)
Line 2: Line 2:
'''Internet Protocol flow information export''' is the general term for methods to collect and report [[flow (Internet Protocol)]] statistics.<ref name=RFC3917>{{citation
'''Internet Protocol flow information export''' is the general term for methods to collect and report [[flow (Internet Protocol)]] statistics.<ref name=RFC3917>{{citation
  | author = Quittek, J., Zseby, T., Claise, B., and S. Zander,
  | author = Quittek, J., Zseby, T., Claise, B., and S. Zander,
  | title = Requirements for IP Flow Information Export  
  | title = Requirements for IP Flow Information Export
  | id = RFC 3917
  | id = RFC 3917
  | date = October 2004  
  | date = October 2004  
Line 14: Line 14:
  | date = October 2004
  | date = October 2004
  | url = http://www.ietf.org/rfc/rfc3955.txt}}</ref>  both originally designed for the IETF, as well as proprietary flow export methods put into the public domain.  
  | url = http://www.ietf.org/rfc/rfc3955.txt}}</ref>  both originally designed for the IETF, as well as proprietary flow export methods put into the public domain.  
A protocol specification was approved in January 2008,<ref name=RFC5101>{{citation
| editor = B. Claise
| title = Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information
| id = RFC 5101
| date = January 2008
| url = http://www.ietf.org/rfc/rfc3955.txt}}</ref> along with a range of supporting specifications.  The greatest body of operational experience with this function came from Cisco's NetFlow, especially with Version 5, an ancestor of the Version 9 submitted to the IETF, and the applicability section of this article will discuss lessons learned both from standards, and from widely used proprietary methods.
==Candidates==


*Common Reliable Accounting for Network Element (XACCT) <ref name=RFC3423>{{citation
*Common Reliable Accounting for Network Element (XACCT) <ref name=RFC3423>{{citation
  | title= XACCT's Common Reliable Accounting for Network Element (CRANE) Protocol Specification Version 1.0
  | title= XACCT's Common Reliable Accounting for Network Element (CRANE) Protocol Specification Version 1.0
  | author =  Zhang, K. and E. Elkin
  | author =  Zhang, K. and E. Elkin
  | date = November 2002
  | date = November 2002  
  | url = http://www.ietf.org/rfc/rfc3423.txt}}</ref>
  | url = http://www.ietf.org/rfc/rfc3423.txt}}</ref>
*(DIAMETER) <ref name=RFC3588>{{citation
*(DIAMETER) <ref name=RFC3588>{{citation
Line 38: Line 29:
  | title = Network Data  Management - Usage (NDM-U) For IP-Based Services Version 3.1
  | title = Network Data  Management - Usage (NDM-U) For IP-Based Services Version 3.1
  | date = April 2002 | url =  http://www.ipdr.org/documents/NDM-U_3.1.pdf}}</ref>
  | date = April 2002 | url =  http://www.ipdr.org/documents/NDM-U_3.1.pdf}}</ref>
*Light-weight Flow Accounting  Protocol Specification Version 5.0<ref name=RFC3588>{{citation
*Light-weight Flow Accounting  Protocol Specification Version 5.0<ref name=RFC3588 />
| title= Light-weight Flow Accounting  Protocol Specification Version 5.0
| author = Calato, P. and M. MacFaden
| date = July 2002
| url = http://www.ietf.org/rfc/rfc3588.txt}}</ref>
*NetFlow Services Export Version 9 (Cisco Systems) <ref name=RFC3954>{{citation
*NetFlow Services Export Version 9 (Cisco Systems) <ref name=RFC3954>{{citation
  | title= Cisco Systems NetFlow Services Export Version 9
  | title= Cisco Systems NetFlow Services Export Version 9
Line 51: Line 38:


==References==
==References==
{{reflist|2}}
{{reflist|2}}[[Category:Suggestion Bot Tag]]

Latest revision as of 11:00, 2 September 2024

This article is developing and not approved.
 Main Article
 Discussion
Related Articles  [?]
Bibliography  [?]
External Links  [?]
Citable Version  [?]
 
https://en.citizendium.org/wiki/index.php?title=Internet_Protocol_flow_information_export&printable=yes
This editable Main Article is under development and subject to a disclaimer.

Internet Protocol flow information export is the general term for methods to collect and report flow (Internet Protocol) statistics.[1] In 2004, the Internet Engineering Task Force (IETF) IPFIX project [2] analyzed methods,[3] both originally designed for the IETF, as well as proprietary flow export methods put into the public domain.

  • Common Reliable Accounting for Network Element (XACCT) [4]
  • (DIAMETER) [5]
  • Internet Protocol Detail Record (IPDR)[6]
  • Light-weight Flow Accounting Protocol Specification Version 5.0[5]
  • NetFlow Services Export Version 9 (Cisco Systems) [7]


References

  1. ↑ Quittek, J., Zseby, T., Claise, B., and S. Zander, (October 2004), Requirements for IP Flow Information Export, RFC 3917
  2. ↑ IP Flow Information Export (ipfix), Internet Engineering Task Force
  3. ↑ S. Leinen (October 2004), Evaluation of Candidate Protocols for IP Flow Information Export (IPFIX), RFC 3955
  4. ↑ Zhang, K. and E. Elkin (November 2002), XACCT's Common Reliable Accounting for Network Element (CRANE) Protocol Specification Version 1.0
  5. ↑ 5.0 5.1 Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko (September 2003), Diameter Base Protocol
  6. ↑ Internet Protocol Detail Record Organization (April 2002), Network Data Management - Usage (NDM-U) For IP-Based Services Version 3.1
  7. ↑ B. Claise, ed. (October 2004), Cisco Systems NetFlow Services Export Version 9
Retrieved from "https://citizendium.org/wiki/index.php?title=Internet_Protocol_flow_information_export&oldid=976259"