Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Path Segment Identifiers (SIDs) with MPLS Data Planes
draft-xp-mpls-spring-lsp-ping-path-sid-00

Document Type Active Internet-Draft (individual)
Authors Xiao Min  , Shaofu Peng 
Last updated 2020-10-30
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                                                X. Min
Internet-Draft                                                 P. Shaofu
Intended status: Standards Track                               ZTE Corp.
Expires: May 3, 2021                                    October 30, 2020

Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Path
            Segment Identifiers (SIDs) with MPLS Data Planes
               draft-xp-mpls-spring-lsp-ping-path-sid-00

Abstract

   Path Segment is a type of SR segment, which is used to identify an SR
   path.  This document provides Target Forwarding Equivalence Class
   (FEC) stack TLV definitions for Path Segment Identifiers.

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 May 3, 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Min & Shaofu               Expires May 3, 2021                  [Page 1]
Internet-Draft       LSP Ping/Trace for SR Path SID         October 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   2
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
     2.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Path Segment ID Sub-TLV . . . . . . . . . . . . . . . . . . .   3
     3.1.  SR Candidate Path's Path SID  . . . . . . . . . . . . . .   3
     3.2.  SR Segment List's Path SID  . . . . . . . . . . . . . . .   6
   4.  Path-SID FEC Validation . . . . . . . . . . . . . . . . . . .   8
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  15
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  15
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   Path Segment is a type of SR segment, which is used to identify an SR
   path.  Path Segment in MPLS based segment routing network is defined
   in [I-D.ietf-spring-mpls-path-segment].

   When Path Segment is used, it's inserted by the ingress node of the
   SR path, and then processed by the egress node of the SR path.  The
   position of Path Segment Label within the MPLS label stack is
   immediately following the segment list of the SR path.  Note that the
   Path Segment would not be popped up until it reaches the egress node.

   This document provides Target Forwarding Equivalence Class (FEC)
   stack TLV definitions for Path-SIDs.  Procedures for LSP Ping and
   Traceroute as defined in [RFC8287] and [RFC8690] are applicable to
   Path-SIDs as well.

2.  Conventions

2.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Min & Shaofu               Expires May 3, 2021                  [Page 2]
Internet-Draft       LSP Ping/Trace for SR Path SID         October 2020

2.2.  Terminology

   This document uses the terminology defined in [RFC8402] and
   [RFC8029], readers are expected to be familiar with those terms.

3.  Path Segment ID Sub-TLV

   Analogous to what's defined in Section 5 of [RFC8287] and Section 4
   of [I-D.ietf-mpls-sr-epe-oam], two new sub-TLVs are defined for the
Show full document text