Skip to main content

Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc: Internet Architecture Board <>,
    RFC Editor <>, 
    ipfix mailing list <>, 
    ipfix chair <>
Subject: Protocol Action: 'Specification of the IPFIX Protocol 
         for the Exchange of IP Traffic Flow Information' to Proposed 

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 

The IESG contact persons are Dan Romascanu and Ron Bonica.

A URL of this Internet-Draft is:

Ballot Text

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:


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

2. Add to Section 14.1 the following two normative references: 


   [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.

RFC Editor Note