Echo Request/Reply for Enabled In-situ OAM Capabilities
draft-xiao-ippm-ioam-conf-state-08

Document Type Active Internet-Draft (candidate for ippm WG)
Authors Xiao Min  , Greg Mirsky  , Lei Bo 
Last updated 2021-01-20
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream WG state Call For Adoption By WG Issued
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
IPPM Working Group                                                X. Min
Internet-Draft                                                 G. Mirsky
Intended status: Standards Track                               ZTE Corp.
Expires: July 24, 2021                                             L. Bo
                                                           China Telecom
                                                        January 20, 2021

        Echo Request/Reply for Enabled In-situ OAM Capabilities
                   draft-xiao-ippm-ioam-conf-state-08

Abstract

   This document describes an extension to the echo request/reply
   mechanisms used in IPv6, MPLS and SFC environments, which can be used
   within an IOAM domain, allowing the IOAM encapsulating node to
   acquire the enabled IOAM capabilities of each IOAM transit node and/
   or IOAM decapsulating node.

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 July 24, 2021.

Copyright Notice

   Copyright (c) 2021 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

Min, et al.               Expires July 24, 2021                 [Page 1]
Internet-Draft       Ping Enabled IOAM Capabilities         January 2021

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   4
     2.2.  Abbreviations . . . . . . . . . . . . . . . . . . . . . .   4
   3.  IOAM Capabilities Formats . . . . . . . . . . . . . . . . . .   5
     3.1.  IOAM Capabilities Query TLV in the Echo Request . . . . .   5
     3.2.  IOAM Capabilities Response TLV in the Echo Reply  . . . .   6
       3.2.1.  IOAM Pre-allocated Tracing Capabilities sub-TLV . . .   7
       3.2.2.  IOAM Incremental Tracing Capabilities sub-TLV . . . .   8
       3.2.3.  IOAM Proof of Transit Capabilities sub-TLV  . . . . .   9
       3.2.4.  IOAM Edge-to-Edge Capabilities sub-TLV  . . . . . . .  10
       3.2.5.  IOAM DEX Capabilities sub-TLV . . . . . . . . . . . .  11
       3.2.6.  IOAM End-of-Domain sub-TLV  . . . . . . . . . . . . .  12
   4.  Operational Guide . . . . . . . . . . . . . . . . . . . . . .  13
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
     6.1.  IOAM SoR Capability Registry  . . . . . . . . . . . . . .  14
     6.2.  IOAM TSF+TSL Capability Registry  . . . . . . . . . . . .  15
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  15
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  16
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   The Data Fields for In-situ OAM (IOAM) [I-D.ietf-ippm-ioam-data]
   defines data fields that record 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".
   In contrast, the device which removes the IOAM data container is
   referred to as the "IOAM decapsulating node".  Nodes within the
Show full document text