RFC 8038: Exporting MIB Variables Using the IP Flow Information Export (IPFIX) Protocol
In plain English — editorial summary, not part of the RFC
This document specifies a way to complement IP Flow Information Export (IPFIX) Data Records with Management Information Base (MIB) objects, avoiding the need to define new IPFIX Information Elements for existing MIB objects that are already fully specified. Two IPFIX Options Templates, as well as a method for creating IPFIX Options Templates that are used to export the extra data required to fully describe Simple Network Management Protocol (SNMP) MIB objects in IPFIX, are specified herein.
Document record
- Document ID
- RFC8038
- Published
- May 2017
- Authors
- P. Aitken; B. Claise; S. B S; C. McDowall; J. Schoenwaelder
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 85
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8503BGP/MPLS Layer 3 VPN Multicast Management Information BaseCurrent
December 2018
- RFC 7133Information Elements for Data Link Layer Traffic MeasurementCurrent
May 2014
- RFC 6727Definitions of Managed Objects for Packet SamplingCurrent
October 2012
- RFC 6615Definitions of Managed Objects for IP Flow Information ExportCurrent
June 2012
- RFC 5066Ethernet in the First Mile Copper (EFMCu) Interfaces MIBUpdated
November 2007
- RFC 4712Transport Mappings for Real-time Application Quality-of-Service Monitoring (RAQMON) Protocol Data Unit (PDU)Updated
October 2006
- RFC 4682Multimedia Terminal Adapter (MTA) Management Information Base for PacketCable- and IPCablecom-Compliant DevicesUpdated
December 2006
- RFC 4547Event Notification Management Information Base for Data over Cable Service Interface Specifications (DOCSIS)-Compliant Cable Modems and Cable Modem Termination SystemsUpdated
June 2006
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?