Exporting MIB Variables Using the IP Flow Information Export (IPFIX) Protocol (RFC8038)
Original Publication Date: 2017-May-01
Included in the Prior Art Database: 2017-May-03
Internet Society Requests For Comment (RFCs)
P. Aitken: AUTHOR [+6]
Data Types. The only new encoding reference in this document is that Object Identifiers (OIDs) will be encoded as per ASN.1/BER [X.690] in an octetArray.
Internet Engineering Task Force (IETF) P. Aitken, Ed. Request for Comments: 8038 Brocade Category: Standards Track B. Claise ISSN: 2070-1721 Cisco Systems, Inc. S. B S Mojo Networks, Inc. C. McDowall Brocade J. Schoenwaelder Jacobs University Bremen May 2017
Exporting MIB Variables Using the IP Flow Information Export (IPFIX) Protocol
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc8038.
Aitken, et al. Standards Track [Page 1]
RFC 8038 Exporting MIB Variables with IPFIX May 2017
Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.