Extended Length Message Support for IP Flow Information Export (IPFIX)
draft-li-opsawg-ipfix-extended-message-00

Document Type Expired Internet-Draft (individual)
Last updated 2018-01-01 (latest revision 2017-06-30)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-li-opsawg-ipfix-extended-message-00.txt

Abstract

The specification of the IP Flow Information Export (IPFIX) Protocol [RFC7011] defines an IPFIX Message length of 16 bits. As new Information Elements (IEs) are introduced in IPFIX to export long information, such as the BGP community information [I-D.ietf-opsawg-ipfix-bgp-community], an IPFIX Message no longer has sufficient space to fit all the information of a specific flow. This document updates the IPFIX specification by extending the IPFIX Message length from 16 bits to 32 bits. For backwards compatibility, a new version of IPFIX (i.e., 11) is introduced to support the 32-bit Message length.

Authors

Zhenqiang Li (li_zhenqiang@hotmail.com)
Paul Aitken (paitken@brocade.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)