Specification of the IP Flow Information Export (IPFIX) File Format
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: IETF-Announce <firstname.lastname@example.org> Cc: Internet Architecture Board <email@example.com>, RFC Editor <firstname.lastname@example.org>, ipfix mailing list <email@example.com>, ipfix chair <firstname.lastname@example.org> Subject: Protocol Action: 'Specification of the IPFIX File Format' to Proposed Standard The IESG has approved the following document: - 'Specification of the IPFIX File Format ' <draft-ietf-ipfix-file-05.txt> as a Proposed Standard This document is the product of the IP Flow Information Export Working Group. The IESG contact persons are Dan Romascanu and Ron Bonica. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipfix-file-05.txt
Technical Summary This document describes a file format for the storage of flow data based upon the IPFIX Protocol. It proposes a set of requirements for flat-file, binary flow data file formats, then specifies the IPFIX File format to meet these requirements based upon IPFIX Messages. This IPFIX File format is designed to facilitate interoperability and reusability among a wide variety of flow storage, processing, and analysis tools. Working Group Summary Work started on this document in 2006, and has gone through several revisions in response to mailing list discussion. Originally it included the material about 'exporting type information,' but the WG split it out into a seperate RFC to make it more easily accessible for other uses. The WG has reached a clear consensus on this draft. Document Quality This document has been reviwed by Benoit Claise, Paul Aitken, Andrew Johnson, and Gerhard Muenz, as well as by the WG chairs. Vijay K. Gurbani reviewed the document on behaf of GenART. It specifies a file format for IPFIX data, making the point that this is simply another data transport for IPFIX. It does not make any changes to the IPFIX protocol. Personnel Nevil Brownlee is the Protocol Shepherd, Dan Romascanu is the shepherding AD. RFC Editor Note Section 9.1: OLD: eContentType id-ct-anyContentType, -- (1.2.840.1135184.108.40.206.1.0) NEW: eContentType id-data, -- (1.2.840.1135220.127.116.11) Section 9.1.4: OLD: The EncapsulatedContentInfo structure contains a content type identifier. Since a detached signature is being created, it does not encapsulate the Internet-Draft. The fields of EncapsulatedContentInfo are as follows: eContentType is an object identifier that uniquely specifies the content type. The content type associated with the plain text file MUST be id-ct-anyContentType (1.2.840.113518.104.22.168.1.0). NEW: The EncapsulatedContentInfo structure contains a content type identifier. Since a detached signature is being created, it does not encapsulate the IPFIX File. The fields of EncapsulatedContentInfo are as follows: eContentType is an object identifier that uniquely specifies the content type. The content type associated with IPFIX File MUST be id-data (1.2.840.113522.214.171.124).