IP Flow Information Export (ipfix)Last Modified: 2011-08-18 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. The IPFIX WG has developed a mediation framework, that defines IPFIX mediators for processing flow records for various purposes including aggregation, anonymization, etc. For configuring IPFIX devices, a YANG module has been developed. 1. Having a solid standardized base for IPFIX deployment and operation and several existing implementations, the IPFIX WG will revisit the IPFIX protocol specifications (RFC 5101) and the IPFIX information element specification (RFC 5102) in order to in order to advance them to the next stage on the standards track. All following items 2.-7. will be in line with the revised versions of the IPFIX protocol specifications and the IPFIX information model. 2. In order to provide guidelines to developers and reviewers (including IE doctors) of new IPFIX information elements and for better defining the process of registering new information elements at IANA the IPFIX WG will create an information element developers and reviewers guideline document. 3. The export of IPFIX flow records from IPFIX mediators introduces a set of potential issues at the protocol level, such as the loss of information on the original exporter, loss of base time information, loss of original options template information, etc. The IPFIX WG will define a set of specifications for applying the IPFIX protocol at mediators, including new specifications for protocol issues not envisioned by the IPFIX protocol itself. 4.In order to support the aggregation of flow records at IPFIX mediators the IPFIX WG will define how to export aggregated flow information using IPFIX. An aggregated flow is essentially an IPFIX flow representing packets from multiple original Flows sharing some set of common properties. 5. The IPFIX WG will investigate the use of the IPFIX protocol for exporting MIB objects, avoiding the need to define new IPFIX information elements for existing management information base objects that are already fully specified. This method requires the specification of new template set and options template sets to allow the export of MIB objects along with IPFIX information elements. 6. The IPFIX MIB module (RFC 5815) defined a way to register packet selector functions at IANA. The WG agreed that another method would be preferable that requires a minor change of RFC 5815. The IPFIX WG will produce a new version of RFC 5815 with small modifications of the IANA actions and DESCRIPTION clauses in the MIB modules. 7. Operational experiences showed that it would be useful to define several new information elements for data link monitoring covering frame size, type, sections of frames, and VLAN information. The IPFIX WG will create a document defining these new information elements. Goals and Milestones:
Internet-Drafts:IPFIX Export per SCTP Stream (58667 bytes)Configuration Data Model for IPFIX and PSAMP (278935 bytes) Flow Selection Techniques (81952 bytes) Definitions of Managed Objects for Packet Sampling (57766 bytes) Definitions of Managed Objects for IP Flow Information Export (137997 bytes) Flow Aggregation for the IP Flow Information Export (IPFIX) Protocol (105443 bytes) Guidelines for Authors and Reviewers of IPFIX Information Elements (67728 bytes) Specification of the IP Flow Information eXport (IPFIX) Protocol for the Exchange of IP Traffic Flow Information (165389 bytes) Specification of the Protocol for IPFIX Mediation (81471 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) updated by RFC 6313 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) updated by RFC 6183 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) IP Flow Information Export (IPFIX) Mediation: Problem Statement (RFC 5982) (56005 bytes) IP Flow Information Export (IPFIX) Mediation: Framework (RFC 6183) (67997 bytes) updates RFC 5470 IP Flow Anonymization Support (RFC 6235) (112595 bytes) Export of Structured Data inIP Flow Information Export (IPFIX) (RFC 6313) (163360 bytes) updates RFC 5102 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||