Extended OAM to Carry In-situ OAM Configuration Data
draft-xiao-ippm-ioam-conf-state-01

Document Type Active Internet-Draft (individual)
Last updated 2018-09-12
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 Working Group                                                X. Min
Internet-Draft                                                 G. Mirsky
Intended status: Standards Track                                     ZTE
Expires: March 16, 2019                               September 12, 2018

          Extended OAM to Carry In-situ OAM Configuration Data
                   draft-xiao-ippm-ioam-conf-state-01

Abstract

   This document describes an extension for OAM packet such as IP Ping
   (ICMP [RFC0792] or ICMPv6 [RFC4443]) and MPLS LSP Ping [RFC8029],
   which can be used within an IOAM domain, allowing the IOAM
   encapsulating node to acquire IOAM configuration data of each IOAM
   transit node and/or IOAM decapsulating node easily and dynamically.

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 March 16, 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
   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.

Min & Mirsky             Expires March 16, 2019                 [Page 1]
Internet-Draft    Extended OAM to Carry IOAM Conf Data    September 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Conventions Used in This Document . . . . . . . . . . . .   3
       1.1.1.  Terminology . . . . . . . . . . . . . . . . . . . . .   3
       1.1.2.  Requirements Language . . . . . . . . . . . . . . . .   3
   2.  IOAM Configuration Data Formats . . . . . . . . . . . . . . .   3
     2.1.  IOAM Configuration Data TLV . . . . . . . . . . . . . . .   3
       2.1.1.  IOAM Tracing Configuration Data sub-TLV . . . . . . .   4
       2.1.2.  IOAM Proof of Transit Configuration Data sub-TLV  . .   6
       2.1.3.  IOAM Edge-to-Edge Configuration Data sub-TLV  . . . .   7
       2.1.4.  IOAM End-of-Domain sub-TLV  . . . . . . . . . . . . .   8
   3.  Operational Guide . . . . . . . . . . . . . . . . . . . . . .   9
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   The Data Fields for In-situ OAM (IOAM) [I-D.ietf-ippm-ioam-data]
   defines data fields for IOAM which records OAM information within the
   packet while the packet traverses a particular network domain, which
   is called an IOAM domain.  IOAM can be used to complement OAM
   mechanisms based on, e.g., ICMP or other types of probe packets, and
   IOAM mechanisms can be leveraged where mechanisms using, e.g., ICMP
   do not apply or do not offer the desired results.

   As specified in [I-D.ietf-ippm-ioam-data], within the IOAM-domain,
   the IOAM data may be updated by network nodes that the packet
   traverses.  The device which adds an IOAM data container to the
   packet to capture IOAM data is called the "IOAM encapsulating node",
   whereas the device which removes the IOAM data container is referred
   to as the "IOAM decapsulating node".  Nodes within the domain which
   are aware of IOAM data and read and/or write or process the IOAM data
   are called "IOAM transit nodes".  Both the IOAM encapsulating node
   and the decapsulating node are referred to as domain edge devices,
   which can be hosts or network devices.

   In order to add accurate IOAM data container to the packet, the IOAM
   encapsulating node needs to know IOAM configurations at the IOAM
   transit nodes in a whole, e.g., how many IOAM transit nodes will add
   tracing data and what kinds of data fields will be added.  Static
   configuration at the IOAM encapsulating node is a way to address
Show full document text