Segment Routing with MPLS Data Plane Encapsulation for In-situ OAM Data
draft-gandhi-spring-ioam-sr-mpls-02

Document Type Active Internet-Draft (individual)
Last updated 2019-08-22
Stream (None)
Intended RFC status (None)
Formats plain text pdf 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)
SPRING Working Group                                      R. Gandhi, Ed.
Internet-Draft                                                    Z. Ali
Intended status: Standards Track                             C. Filsfils
Expires: February 23, 2020                                  F. Brockners
                                                     Cisco Systems, Inc.
                                                                  B. Wen
                                                                V. Kozak
                                                                 Comcast
                                                         August 22, 2019

          Segment Routing with MPLS Data Plane Encapsulation 
                          for In-situ OAM Data 
                  draft-gandhi-spring-ioam-sr-mpls-02

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.  Segment
   Routing (SR) technology leverages the source routing paradigm.  This
   document defines how IOAM data fields are transported with the
   Segment Routing with MPLS data plane (SR-MPLS) encapsulation.  The
   procedures defined are also equally applicable to all other MPLS data
   plane encapsulations.

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 http://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."

Copyright Notice

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

Gandhi, et al.         Expires February 23, 2020                [Page 1]
Internet-Draft     In-situ OAM for SR-MPLS Data plane    August 22, 2019

   (http://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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Conventions  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     2.1.  Requirement Language . . . . . . . . . . . . . . . . . . .  3
     2.2.  Abbreviations  . . . . . . . . . . . . . . . . . . . . . .  3
   3.  IOAM Data Field Encapsulation in SR-MPLS Header  . . . . . . .  3
   4.  Procedure for Edge-to-Edge IOAM  . . . . . . . . . . . . . . .  5
     4.1.  Edge-to-Edge IOAM Indicator Labels . . . . . . . . . . . .  6
   5.  Procedure for Hop-by-Hop IOAM  . . . . . . . . . . . . . . . .  7
   6.  Considerations for ECMP  . . . . . . . . . . . . . . . . . . .  7
   7.  Node Capability  . . . . . . . . . . . . . . . . . . . . . . .  7
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  7
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . .  8
   10.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  8
   11.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  8
     11.1.  Normative References  . . . . . . . . . . . . . . . . . .  8
     11.2.  Informative References  . . . . . . . . . . . . . . . . .  9
   Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . .  9
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  9

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.

   Segment Routing (SR) technology leverages the source routing paradigm
   [I-D.ietf-spring-segment-routing-mpls].  A node steers a packet
   through a controlled set of instructions, called segments, by
Show full document text