MPLS Data Plane Encapsulation for In-situ OAM Data
draft-gandhi-mpls-ioam-sr-03

Document Type Active Internet-Draft (individual)
Authors Rakesh Gandhi  , Zafar Ali  , Clarence Filsfils  , Frank Brockners  , Bin Wen  , Voitek Kozak 
Last updated 2020-09-13
Replaces draft-gandhi-spring-ioam-sr-mpls
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)
MPLS Working Group                                        R. Gandhi, Ed.
Internet-Draft                                                    Z. Ali
Intended status: Standards Track                             C. Filsfils
Expires: March 17, 2021                                     F. Brockners
                                                     Cisco Systems, Inc.
                                                                  B. Wen
                                                                V. Kozak
                                                                 Comcast
                                                      September 13, 2020

           MPLS Data Plane Encapsulation for In-situ OAM Data
                      draft-gandhi-mpls-ioam-sr-03

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 using the MPLS
   data plane encapsulation, 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 March 17, 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

Gandhi, et al.           Expires March 17, 2021                 [Page 1]
Internet-Draft       In-situ OAM for MPLS Data plane      September 2020

   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
     3.1.  Indicator Labels  . . . . . . . . . . . . . . . . . . . .   6
   4.  Procedure for Edge-to-Edge IOAM . . . . . . . . . . . . . . .   6
     4.1.  Edge-to-Edge IOAM Indicator Label Allocation  . . . . . .   7
   5.  Procedure for Hop-by-Hop IOAM . . . . . . . . . . . . . . . .   7
     5.1.  Hop-by-Hop IOAM Indicator Label Allocation  . . . . . . .   8
   6.  Considerations for ECMP . . . . . . . . . . . . . . . . . . .   8
   7.  Node Capability . . . . . . . . . . . . . . . . . . . . . . .   9
   8.  Data Packets with SR-MPLS Header  . . . . . . . . . . . . . .   9
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     11.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  12
   Contributors  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

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
   packets rather than being sent within the probe packets specifically
   dedicated to OAM or Performance Measurement (PM).  The IOAM data
   fields are defined in [I-D.ietf-ippm-ioam-data], and can be used for
   various use-cases for OAM and PM.  The IOAM data fields are further
   updated in [I-D.ietf-ippm-ioam-direct-export] for direct export use-
   cases and in [I-D.ietf-ippm-ioam-flags] for Loopback and Active
Show full document text