RFC 5102: Information Model for IP Flow Information Export
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7012.
Current version: RFC 7012 — Information Model for IP Flow Information Export (IPFIX)
In plain English — editorial summary, not part of the RFC
This memo defines an information model for the IP Flow Information eXport (IPFIX) protocol. It is used by the IPFIX protocol for encoding measured traffic information and information related to the traffic Observation Point, the traffic Metering Process, and the Exporting Process. Although developed for the IPFIX protocol, the model is defined in an open way that easily allows using it in other protocols, interfaces, and applications. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5102
- Published
- January 2008
- Authors
- J. Quittek; S. Bryant; B. Claise; P. Aitken; J. Meyer
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 171
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5476Packet Sampling (PSAMP) Protocol SpecificationsCurrent
March 2009
- RFC 7133Information Elements for Data Link Layer Traffic MeasurementCurrent
May 2014
- RFC 5101Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow InformationObsoleted
January 2008
- RFC 5470Architecture for IP Flow Information ExportUpdated
March 2009
- RFC 5471Guidelines for IP Flow Information Export (IPFIX) TestingCurrent
March 2009
- RFC 5475Sampling and Filtering Techniques for IP Packet SelectionCurrent
March 2009
- RFC 5477Information Model for Packet Sampling ExportsCurrent
March 2009
- RFC 5815Definitions of Managed Objects for IP Flow Information ExportObsoleted
April 2010
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?