Echo Request/Reply for Enabled In-situ OAM Capabilities
draft-xiao-ippm-ioam-conf-state-07
IPPM Working Group X. Min
Internet-Draft G. Mirsky
Intended status: Standards Track ZTE Corp.
Expires: March 8, 2021 L. Bo
China Telecom
September 4, 2020
Echo Request/Reply for Enabled In-situ OAM Capabilities
draft-xiao-ippm-ioam-conf-state-07
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 March 8, 2021.
Copyright Notice
Copyright (c) 2020 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 March 8, 2021 [Page 1]
Internet-Draft Echo Request/Reply for IOAM Capa September 2020
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3
3. IOAM Capabilities Formats . . . . . . . . . . . . . . . . . . 4
3.1. IOAM Capabilities TLV in Echo Request . . . . . . . . . . 4
3.2. IOAM Capabilities TLV in Echo Reply . . . . . . . . . . . 5
3.2.1. IOAM Pre-allocated Tracing Capabilities sub-TLV . . . 6
3.2.2. IOAM Incremental Tracing Capabilities sub-TLV . . . . 7
3.2.3. IOAM Proof of Transit Capabilities sub-TLV . . . . . 8
3.2.4. IOAM Edge-to-Edge Capabilities sub-TLV . . . . . . . 9
3.2.5. IOAM DEX Capabilities sub-TLV . . . . . . . . . . . . 11
3.2.6. IOAM End-of-Domain sub-TLV . . . . . . . . . . . . . 11
4. Operational Guide . . . . . . . . . . . . . . . . . . . . . . 12
5. Security Considerations . . . . . . . . . . . . . . . . . . . 13
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
8. Normative References . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
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.
Show full document text