Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information
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 Protocol for the Exchange of IP Traffic Flow Information' to Proposed Standard The IESG has approved the following document: - 'Specification of the IPFIX Protocol for the Exchange of IP Traffic Flow Information ' <draft-ietf-ipfix-protocol-27.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-protocol-27.txt
Technical Summary This document specifies the IPFIX protocol that serves for transmitting IP traffic flow information over the network. In order to transmit IP traffic flow information from an exporting process to an information collecting process, a common representation of flow data and a standard means of communicating them is required. This document describes how the IPFIX data and templates records are carried over a congestion-aware transport protocol from an IPFIX exporting process to an IPFIX collecting process. Working Group Summary This document is a regular WG document. There is strong consensus in the working group that this protocol is well-designed, and suitable for its intended purpose. Protocol Quality The document was thoroughly reviewed by the IPFIX WG. Bert Wijnen performed the AD review. Furthermore, the IPFIX WG has run two interoperability events, with five independent implementations tested and working, demonstrating that the IPFIX documents are of a high technical standard. Note to RFC Editor Please make the following changes: 1. Add at the end of the currect Section 11.3 the following paragraph: NEW: Internationalized domain names (IDN) in either the subjectAltName extension of type dNSName or the most specific Common Name field of the Subject field of the X.509 certificate MUST be encoded using Punycode [RFC3492] as described in Section 4, "Conversion Operations", of [RFC3490]. 2. Add to Section 14.1 the following two normative references: NEW: [RFC3490] Faltstrom, P., Hoffman, P., and A. Costello, "Internationalizing Domain Names in Applications (IDNA)", RFC 3490, March 2003. [RFC3492] Costello, A., "Punycode: A Bootstring encoding of Unicode for use with Internationalized Domain Names in Applications (IDNA)", RFC 3492, March 2003.