RFC 7270: Cisco-Specific Information Elements Reused in IP Flow Information Export (IPFIX)
In plain English — editorial summary, not part of the RFC
This document describes some additional IP Flow Information Export (IPFIX) Information Elements in the range of 1-127, which is the range compatible with field types used by NetFlow version 9 in RFC 3954, as specified in the IPFIX Information Model in RFC 7012.
Document record
- Document ID
- RFC7270
- Published
- June 2014
- Authors
- A. Yourtchenko; P. Aitken; B. Claise
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7133Information Elements for Data Link Layer Traffic MeasurementCurrent
May 2014
- RFC 6728Configuration Data Model for the IP Flow Information Export (IPFIX) and Packet Sampling (PSAMP) ProtocolsCurrent
October 2012
- RFC 6727Definitions of Managed Objects for Packet SamplingCurrent
October 2012
- RFC 6645IP Flow Information Accounting and Export Benchmarking MethodologyCurrent
July 2012
- RFC 6615Definitions of Managed Objects for IP Flow Information ExportCurrent
June 2012
- RFC 8038Exporting MIB Variables Using the IP Flow Information Export (IPFIX) ProtocolCurrent
May 2017
- RFC 6235IP Flow Anonymization SupportCurrent
May 2011
- RFC 8549Export of BGP Community Information in IP Flow Information Export (IPFIX)Current
April 2019
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?