In-situ OAM Data Type Extension
draft-song-ippm-ioam-data-extension-01

Document Type Active Internet-Draft (individual)
Last updated 2018-04-16
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                                                        H. Song, Ed.
Internet-Draft                                                   T. Zhou
Intended status: Standards Track                                  Huawei
Expires: October 18, 2018                                 April 16, 2018

                    In-situ OAM Data Type Extension
                 draft-song-ippm-ioam-data-extension-01

Abstract

   This document describes a proposal which extends in-situ OAM to
   support potential future standard tracing data in addition to those
   currently defined.  We provide use cases to motivate our proposal and
   base the modifications on the latest in-situ OAM header format
   specification.

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 October 18, 2018.

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
   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.

Song & Zhou             Expires October 18, 2018                [Page 1]
Internet-Draft          IOAM Data Type Extension              April 2018

Table of Contents

   1.  Motivation for Data Type Extension  . . . . . . . . . . . . .   2
   2.  Scalable Data Type Extension  . . . . . . . . . . . . . . . .   3
     2.1.  Data Type Bitmap  . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.3.  Consideration for Efficient Data Packing  . . . . . . . .   5
     2.4.  Alternative Data Extension Possibilities  . . . . . . . .   5
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   6
   7.  Informative References  . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Motivation for Data Type Extension

   In-situ OAM (iOAM) [I-D.brockners-inband-oam-requirements] records
   OAM information within user packets while the packets traverse a
   network.  The data types and data formats for in-situ OAM data
   records have been defined in [I-D.ietf-ippm-ioam-data].

   Currently 12 data types and associated formats (including wide format
   and short format of the same data) are defined in
   [I-D.ietf-ippm-ioam-data] .  The presence of data is indicated by a
   16-bit bitmap in the "OAM-Trace-Type" field.

   In the current specification only four bits are left to identify new
   standard data types.  Moreover, some data is forced to be bundled
   together as a single unit to save bitmap space and pack data to the
   ideal size (e.g., the hop limit and the node id are bundled, and the
   ingress interface id and the egress interface id are bundled),
   regardless of the fact that an application may only ask for a part of
   the data.  Last but not the least, each data is forced to be 4-byte
   aligned for easier access, resulting in waste of header space in many
   cases.

   Since the data plane bandwidth, the data plane packet processing, and
   the management plane data handling are all precious yet scarce
   resource, the scheme should strive to be simple and precise.  The
   application should be able to control the exact type and format of
   data it needs to collect and analyze.  It is conceivable that more
   types of data may be introduced in the future.  However, the current
   scheme cannot support it after all the bits in the bitmap are used
   up.

   For example, when a flow traverses a series of middleboxes (e.g.,
   Firewall, NAT, and load balancer), its identity (e.g., the 5-tuple)

Song & Zhou             Expires October 18, 2018                [Page 2]
Show full document text