Additional data fields for IOAM Trace Option Types
draft-gafni-ippm-ioam-additional-data-fields-00

Document Type Active Internet-Draft (individual)
Authors Barak Gafni  , Hongqiang Liu  , Rui Miao  , Mickey Spiegel 
Last updated 2020-11-02
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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                                                            B. Gafni
Internet-Draft                                                    Nvidia
Intended status: Standards Track                                  H. Liu
Expires: May 6, 2021                                             R. Miao
                                                           Alibaba Group
                                                              M. Spiegel
                               Barefoot Networks, an Intel
      company
                                                       November 02, 2020

           Additional data fields for IOAM Trace Option Types
            draft-gafni-ippm-ioam-additional-data-fields-00

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 additional data fields and associated data types to be
   added to the IOAM data fileds described in [I-D.ietf-ippm-ioam-data].
   In-situ OAM data fields can be encapsulated into a variety of
   protocols such as NSH, Segment Routing, Geneve, IPv6 (via extension
   header), or IPv4.

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 May 6, 2021.

Copyright Notice

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

Gafni, et al.              Expires May 6, 2021                  [Page 1]
Internet-DraftAdditional data fields for In-situ OAM Trace November 2020

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   2
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
     2.2.  Abbreviations . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Additional Data Fields  . . . . . . . . . . . . . . . . . . .   3
     3.1.  IOAM Trace Option-Types Ammendments . . . . . . . . . . .   3
     3.2.  The Additional IOAM Node Data Fields and Associated
           Formats . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   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 is
   adding additional data fields that can be reported by the network as
   part of IOAM.

2.  Conventions

2.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Gafni, et al.              Expires May 6, 2021                  [Page 2]
Internet-DraftAdditional data fields for In-situ OAM Trace November 2020

2.2.  Abbreviations

   Abbreviations used in this document:

   IOAM:      In-situ Operations, Administration, and Maintenance

3.  Additional Data Fields

   This draft extends [I-D.ietf-ippm-ioam-data] with additional data
   fields.  The additional suggested data fields are:

   o  Transmitted Bytes from an interface

   o  Speed of an interface
Show full document text