IP Flow Information Export (ipfix)Last Modified: 2010-07-12 Additional information is available at tools.ietf.org/wg/ipfix
Chair(s):Operations and Management Area Director(s):Operations and Management Area Advisor:Mailing Lists:General Discussion: ipfix@ietf.orgTo Subscribe: http://www.ietf.org/mailman/listinfo/ipfix Archive: http://www.ietf.org/mail-archive/web/ipfix Description of Working Group:The IPFIX working group has specified the Information Model (to describeIP flows) and the IPFIX protocol (to transfer IP flow data from IPFIX exporters to collectors). Several implementers have already built applications using the IPFIX protocol. As a result of a series of IPFIX interoperability testing events the WG has produced guidelines for IPFIX implementation and testing as well as recommendations for handling special cases such as bidirectional flow reporting and reducing redundancy in flow records. Practical experiences with IPFIX implementations exposed new requirements for the IPFIX protocol that so far have not been addressed by the WG. The major current goal of the WG is developing solutions that meet the new requirements without modifying the core IPFIX protocol specifications. 1. The IPFIX WG has developed a MIB module for monitoring IPFIX implementations. Means for configuring these devices have not been standardized yet. The WG will develop an XML-based configuration data model that can be used for configuring IPFIX devices and for storing, modifying and managing IPFIX configurations parameter sets. This work will be performed in close collaboration with the NETCONF WG. 2. First applications of IPFIX at large operator networks showed the need for mediation of flow information, for example, for aggregating huge amounts of flow data and for anomymization of flow information. The IPFIX WG will investigate this issue and produce a problem statement and a framework for IPFIX flow mediation. 3. The PSAMP WG has developed a protocol for reporting observed packets. The PSAMP protocol is an extension of the IPFIX protocol. The IPFIX WG will develop a MIB module for monitoring PSAMP implementations. The new MIB module will be an extension of the IPFIX MIB module. 4. Anonymization of flow information has been identified as a requirement for flow information export already in RFC 3917. However, technologies for flow anonymization are still a research issue and have so far not been considered to be mature enough for standardization. As one step in this direction, the IPFIX WG will develop guidelines for the implementation of anonymized data export and storage over IPFIX and define an information model for configuring and reporting anonymization applied at IPFIX devices. 5. The IPFIX and PSAMP WGs have defined standards for selecting observed IP packets and collecting information in flow records. In order to reduce the amount of data to be processed, packet selection methods have been defined. Another method for reducing flow data is flow selection. The IPFIX WG will define methods for flow selection and provide an information model for configuring and reporting flow selection applied at IPFIX devices. 6. Being designed for the export of flow records the IPFIX protocol provides very limited means for structuring information elements within IPFIX records. With the increasing number of IPFIX applications there is a need for exporting more complex information. The IPFIX WG will develop an extension of the IPFIX protocol that supports hierarchically structured data and lists (sequences) of Information Elements in data records. Goals and Milestones:
Internet-Drafts:IPFIX Mediation: Problem Statement (56506 bytes)IPFIX Mediation: Framework (68906 bytes) IPFIX Export per SCTP Stream (58667 bytes) Configuration Data Model for IPFIX and PSAMP (269917 bytes) IP Flow Anonymisation Support (105150 bytes) Export of Structured Data in IPFIX (177934 bytes) Flow Selection Techniques (54667 bytes) Definitions of Managed Objects for Packet Sampling (56052 bytes) Request For Comments:Requirements for IP Flow Information Export (RFC 3917) (81615 bytes)Evaluation of Candidate Protocols for IP Flow Information Export (IPFIX) (RFC 3955) (55143 bytes) Bidirectional Flow Export using IP Flow Information Export (IPFIX) (RFC 5103) (53534 bytes) Information Model for IP Flow Information Export (RFC 5102) (335617 bytes) Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information (RFC 5101) (147196 bytes) IPFIX Implementation Guidelines (RFC 5153) (82845 bytes) Reducing Redundancy in IP Flow Information Export (IPFIX) and Packet Sampling (PSAMP) Reports (RFC 5473) (64654 bytes) IP Flow Information Export (IPFIX) Applicability (RFC 5472) (71379 bytes) Guidelines for IP Flow Information Export (IPFIX) Testing (RFC 5471) (69313 bytes) Architecture for IP Flow Information Export (RFC 5470) (65717 bytes) Exporting Type Information for IPFIX Information Elements (RFC 5610) (42526 bytes) Specification of the IP Flow Information Export (IPFIX) File Format (RFC 5655) (154566 bytes) Definitions of Managed Objects for IP Flow Information Export (RFC 5815) (131258 bytes) |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||