Label Switched Path (LSP) Ping/Traceroute for Segment Routing SIDs with MPLS Data-plane
draft-nainar-mpls-spring-lsp-ping-sids-00

Document Type Active Internet-Draft (individual)
Last updated 2018-10-23
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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)
Network Work group                                         N. Kumar, Ed.
Internet-Draft                                         C. Pignataro, Ed.
Intended status: Standards Track                                F. Iqbal
Expires: April 26, 2019                                           Z. Ali
                                                                   Cisco
                                                        October 23, 2018

Label Switched Path (LSP) Ping/Traceroute for Segment Routing SIDs with
                            MPLS Data-plane
               draft-nainar-mpls-spring-lsp-ping-sids-00

Abstract

   RFC8402 introduces Segment Routing architecture that leverages source
   routing and tunneling paradigms and can be directly applied to the
   Multi Protocol Label Switching (MPLS) data plane.  A node steers a
   packet through a controlled set of instructions called segments, by
   prepending the packet with Segment Routing header.  SR architecture
   defines different types of segments with different forwarding
   semantics associated.

   RFC8287 defines the extensions to MPLS LSP Ping and Traceroute for
   Segment Routing IGP-Prefix and IGP-Adjacency Segment Identifier
   (SIDs) with an MPLS data plane.  RFC8287 defines the Target FEC Stack
   Sub-TLVs and the procedures to apply RFC8029 on SR architecture with
   MPLS data plane.

   This document defines the Target FEC Stack Sub-TLVs and the extension
   required for other SR Segments.

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 April 26, 2019.

Kumar, et al.            Expires April 26, 2019                 [Page 1]
Internet-Draft     LSP Ping/Trace for SR SIDs on MPLS       October 2018

Copyright Notice

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Requirements notation . . . . . . . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Segment ID sub-TLV  . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  BGP Prefix Segment ID . . . . . . . . . . . . . . . . . .   4
     4.2.  BGP Peering Segment - Peer-Node-SID . . . . . . . . . . .   4
     4.3.  BGP Peering Segment - Peer-Adj-SID  . . . . . . . . . . .   5
     4.4.  BGP Peering Segment - Peer-Set-SID  . . . . . . . . . . .   7
       4.4.1.  Peer Set Sub-TLV  . . . . . . . . . . . . . . . . . .   8
     4.5.  Path Binding SID  . . . . . . . . . . . . . . . . . . . .   9
     4.6.  Multicast Replication . . . . . . . . . . . . . . . . . .  10
   5.  Procedures  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     5.1.  BGP Prefix SID  . . . . . . . . . . . . . . . . . . . . .  10
     5.2.  BGP Peering Segment Sub-TLVs  . . . . . . . . . . . . . .  10
       5.2.1.  Initiator Node Procedures . . . . . . . . . . . . . .  10
       5.2.2.  Responder Node Procedures . . . . . . . . . . . . . .  11
     5.3.  Path Binding SID  . . . . . . . . . . . . . . . . . . . .  11
       5.3.1.  Initiator Node Procedures . . . . . . . . . . . . . .  11
       5.3.2.  Responder Node Procedures . . . . . . . . . . . . . .  11
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   8.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .  12
   9.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  12
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  12
     10.2.  Informative References . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14
Show full document text