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

Document Type Active Internet-Draft (individual)
Last updated 2017-06-30
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
opsawg                                                             Z. Li
Internet-Draft                                              China Mobile
Intended status: Standards Track                               P. Aitken
Expires: January 1, 2018            Brocade Communications Systems, Inc.
                                                           June 30, 2017

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

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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 1, 2018.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of

Li & Aitken              Expires January 1, 2018                [Page 1]
Internet-Draft  Extended Length Message Support for IPFIX      June 2017

   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  IPFIX Extended Length Message . . . . . . . . . . . . . . . .   3
     3.1.  IPFIX Extended Length Message Header  . . . . . . . . . .   3
     3.2.  IPFIX Extended Length Set Header  . . . . . . . . . . . .   3
     3.3.  IPFIX Extended Variable-Length IE . . . . . . . . . . . .   4
   4.  Transport Protocol Considerations . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The IP Flow Information Export (IPFIX) Protocol [RFC7011] provides
   network administrators with traffic flow information using the
   Information Elements (IEs) defined in IANA's IPFIX registry
   [IANA-IPFIX].  [RFC7011] specifies an IPFIX Message length of 16
   bits.  As new IEs are introduced in IPFIX to export long information,
   such as the BGP community information
   [I-D.ietf-opsawg-ipfix-bgp-community], one IPFIX Message no longer
   has sufficient space to fit all the information of a specific flow.
   The maximum IPFIX message size needs to be extended beyond 65535
   octets.  This document updates the IPFIX specification by extending
   the IPFIX Message length from 16 bits to 32 bits, which means the
   maximum IPFIX message size is 4 giga bytes.  For backwards
   compatibility, a new version of IPFIX (i.e., 11) is introduced to
   support the 32-bit Message length.

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text