RFC 5472: IP Flow Information Export (IPFIX) Applicability
In plain English — editorial summary, not part of the RFC
In this document, we describe the applicability of the IP Flow Information eXport (IPFIX) protocol for a variety of applications. We show how applications can use IPFIX, describe the relevant Information Elements (IEs) for those applications, and present opportunities and limitations of the protocol. Furthermore, we describe relations of the IPFIX framework to other architectures and frameworks. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5472
- Published
- March 2009
- Authors
- T. Zseby; E. Boschi; N. Brownlee; B. Claise
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 31
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5474A Framework for Packet Selection and ReportingCurrent
March 2009
- RFC 5475Sampling and Filtering Techniques for IP Packet SelectionCurrent
March 2009
- RFC 5477Information Model for Packet Sampling ExportsCurrent
March 2009
- RFC 5779Diameter Proxy Mobile IPv6: Mobile Access Gateway and Local Mobility Anchor Interaction with Diameter ServerCurrent
February 2010
- RFC 5866Diameter Quality-of-Service ApplicationCurrent
May 2010
- RFC 6049Spatial Composition of MetricsUpdated
January 2011
- RFC 6076Basic Telephony SIP End-to-End Performance MetricsCurrent
January 2011
- RFC 6576IP Performance Metrics (IPPM) Standard Advancement TestingCurrent
March 2012
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?