In-situ OAM raw data export with IPFIX
draft-spiegel-ippm-ioam-rawexport-01

Document Type Active Internet-Draft (individual)
Last updated 2018-10-22
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)
ippm                                                          M. Spiegel
Internet-Draft                                         Barefoot Networks
Intended status: Informational                              F. Brockners
Expires: April 25, 2019                                      S. Bhandari
                                                          R. Sivakolundu
                                                                   Cisco
                                                        October 22, 2018

                 In-situ OAM raw data export with IPFIX
                  draft-spiegel-ippm-ioam-rawexport-01

Abstract

   In-situ Operations, Administration, and Maintenance (IOAM) records
   operational and telemetry information in the packet while the packet
   traverses a path between two points in the network.  This document
   discusses how In-situ Operations, Administration, and Maintenance
   (IOAM) information can be exported in raw, i.e. uninterpreted, format
   from network devices to systems, such as monitoring or analytics
   systems using IPFIX.

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 https://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 April 25, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Spiegel, et al.          Expires April 25, 2019                 [Page 1]
Internet-Draft            IOAM raw data export              October 2018

   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
     1.1.  Requirements  . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  IPFIX for IOAM raw data export  . . . . . . . . . . . . . . .   6
     3.1.  Key IPFIX information elements leveraged for IOAM raw
           data export . . . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  New IPFIX information elements leveraged for IOAM raw
           data export . . . . . . . . . . . . . . . . . . . . . . .   7
       3.2.1.  ioamReportFlags . . . . . . . . . . . . . . . . . . .   7
       3.2.2.  ioamEncapsulationType . . . . . . . . . . . . . . . .   7
       3.2.3.  ioamPreallocatedTraceData . . . . . . . . . . . . . .   8
       3.2.4.  ioamIncrementalTraceData  . . . . . . . . . . . . . .   9
       3.2.5.  ioamE2EData . . . . . . . . . . . . . . . . . . . . .   9
       3.2.6.  ioamPOTData . . . . . . . . . . . . . . . . . . . . .  10
       3.2.7.  ipHeaderPacketSectionWithPadding  . . . . . . . . . .  10
       3.2.8.  ethernetFrameSection  . . . . . . . . . . . . . . . .  11
   4.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
     4.1.  Fixed Length IP Packet  . . . . . . . . . . . . . . . . .  12
     4.2.  Variable Length IP Packet (length < 255)  . . . . . . . .  13
     4.3.  Variable Length IP Packet (length > 255)  . . . . . . . .  14
     4.4.  Variable Length ETHERNET Packet (length < 255)  . . . . .  15
     4.5.  Variable Length IP Packet with Fixed Length IOAM
           Incremental Trace Data  . . . . . . . . . . . . . . . . .  16
     4.6.  Variable Length IP Packet with Variable Length IOAM
           Incremental Trace Data  . . . . . . . . . . . . . . . . .  17
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
   6.  Manageability Considerations  . . . . . . . . . . . . . . . .  19
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  19
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  19
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  19
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  19
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  20
Show full document text