MPLS Data Plane Encapsulation for In-situ OAM Data
draft-gandhi-mpls-ioam-sr-05
MPLS Working Group R. Gandhi, Ed.
Internet-Draft Z. Ali
Intended status: Standards Track C. Filsfils
Expires: July 13, 2021 F. Brockners
Cisco Systems, Inc.
B. Wen
V. Kozak
Comcast
January 09, 2021
MPLS Data Plane Encapsulation for In-situ OAM Data
draft-gandhi-mpls-ioam-sr-05
Abstract
In-situ Operations, Administration, and Maintenance (IOAM) records
operational and telemetry information in the data packet while the
packet traverses a path between two nodes in the network. This
document defines how IOAM data fields are transported with MPLS data
plane encapsulation using new Generic Associated Channel (G-ACh),
including Segment Routing (SR) with MPLS data plane (SR-MPLS).
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 13, 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
Gandhi, et al. Expires July 13, 2021 [Page 1]
Internet-Draft In-situ OAM for MPLS Data plane January 2021
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Requirement Language . . . . . . . . . . . . . . . . . . 3
2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3
3. IOAM Data Field Encapsulation in MPLS Header . . . . . . . . 3
4. Edge-to-Edge IOAM . . . . . . . . . . . . . . . . . . . . . . 5
4.1. Edge-to-Edge IOAM Indicator Label . . . . . . . . . . . . 5
4.2. Procedure for Edge-to-Edge IOAM . . . . . . . . . . . . . 5
4.3. Edge-to-Edge IOAM Indicator Label Allocation . . . . . . 6
5. Hop-by-Hop IOAM . . . . . . . . . . . . . . . . . . . . . . . 6
5.1. Hop-by-Hop IOAM Indicator Label . . . . . . . . . . . . . 6
5.2. Procedure for Hop-by-Hop IOAM . . . . . . . . . . . . . . 7
5.3. Hop-by-Hop IOAM Indicator Label Allocation . . . . . . . 8
6. Considerations for IOAM Indicator Label . . . . . . . . . . . 8
6.1. Considerations for ECMP . . . . . . . . . . . . . . . . . 8
6.2. Node Capability . . . . . . . . . . . . . . . . . . . . . 8
6.3. MSD Considerations . . . . . . . . . . . . . . . . . . . 9
6.4. Nested MPLS Encapsulation . . . . . . . . . . . . . . . . 9
7. SR-MPLS Header with IOAM . . . . . . . . . . . . . . . . . . 9
8. Security Considerations . . . . . . . . . . . . . . . . . . . 10
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
10.1. Normative References . . . . . . . . . . . . . . . . . . 11
10.2. Informative References . . . . . . . . . . . . . . . . . 12
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 13
Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction
In-situ Operations, Administration, and Maintenance (IOAM) records
operational and telemetry information within the packet while the
packet traverses a particular network domain. The term "in-situ"
refers to the fact that the IOAM data fields are added to the data
Show full document text