Extended Length Message Support for IP Flow Information Export (IPFIX)
draft-li-opsawg-ipfix-extended-message-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Zhenqiang Li , Paul Aitken | ||
| Last updated | 2018-01-01 (Latest revision 2017-06-30) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)