RFC 7012: Information Model for IP Flow Information Export (IPFIX)
In plain English — editorial summary, not part of the RFC
This document defines the data types and management policy for the information model for the IP Flow Information Export (IPFIX) protocol. This information model is maintained as the IANA "IPFIX Information Elements" registry, the initial contents of which were defined by RFC 5102. This information model 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 this model was developed for the IPFIX protocol, it is defined in an open way that allows it to be easily used in other protocols, interfaces, and applications. This document obsoletes RFC 5102.
Document record
- Document ID
- RFC7012
- Published
- September 2013
- Authors
- B. Claise; B. Trammell
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 24
- Also known as
- —
- Obsoletes:
- RFC 5102
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7011Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow InformationCurrent
September 2013
- RFC 7013Guidelines for Authors and Reviewers of IP Flow Information Export (IPFIX) Information ElementsCurrent
September 2013
- RFC 7014Flow Selection TechniquesCurrent
September 2013
- RFC 7010IPv6 Site Renumbering Gap AnalysisCurrent
September 2013
- RFC 7015Flow Aggregation for the IP Flow Information Export (IPFIX) ProtocolCurrent
September 2013
- RFC 6991Common YANG Data TypesObsoleted
July 2013
- RFC 6988Requirements for Energy ManagementCurrent
September 2013
- RFC 6985IMIX Genome: Specification of Variable Packet Sizes for Additional TestingCurrent
July 2013
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?