Skip to main content

Cisco Systems Export of Application Information in IP Flow Information Export (IPFIX)

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc: RFC Editor <>
Subject: Document Action: 'Cisco Systems Export of Application Information in IPFIX' to Informational RFC (draft-claise-export-application-info-in-ipfix-10.txt)

The IESG has approved the following document:
- 'Cisco Systems Export of Application Information in IPFIX'
  (draft-claise-export-application-info-in-ipfix-10.txt) as Informational

This document has been reviewed in the IETF but is not the product of an
IETF Working Group.

The IESG contact person is Ronald Bonica.

A URL of this Internet Draft is:

Ballot Text

Technical Summary 

  This document's title is "Cisco Systems Export of Application Information in IPFIX".
  It points out that various vendors implement different
  ways of determining the type of application producing a flow, but
  that we need an RFC-specified way of exporting that information
  using IPFIX.  The document describes a taxonomy of application
  types, ordered by 'classification engine IDs.'  These IDs are
  mostly IANA registries, but the document also proposes new one
  called PANA-Lx (where Lx can be L2, L3 or L4) for Proprietary Layer
  3 definitions.  The intention here is that vendors could publish
  their own sets of Application IDs, so that they would be freely

Working Group Summary 

  This is an Individual Submission, but - as mentioned above - it has
  been discussed, and received considerable support in the IPFIX
  Working Group.

Document Quality 

  The document does not define a new protocol, instead it defines a
  set of new IPFIX Information IDs; I see no difficulties with these.


   Document Shepherd is Nevil Browlee

RFC Editor Note