Path Segment in MPLS Based Segment Routing Network
draft-cheng-spring-mpls-path-segment-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2018-07-02 (latest revision 2018-03-05)
Stream (None)
Intended RFC status (None)
Formats plain text 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 Working Group                                           W. Cheng
Internet-Draft                                                   L. Wang
Intended status: Standards Track                                   H. Li
Expires: January 3, 2019                                    China Mobile
                                                                 M. Chen
                                                                  Huawei
                                                               R. Zigler
                                                                Broadcom
                                                                 S. Zhan
                                                                     ZTE
                                                               R. Gandhi
                                                     Cisco Systems, Inc.
                                                           July 02, 2018

           Path Segment in MPLS Based Segment Routing Network
                draft-cheng-spring-mpls-path-segment-02

Abstract

   An SR path is identified by an SR segment list, one or partial
   segments of the list cannot uniquely identify the SR path.  Path
   identification is the precondition of performance measurement (PM) of
   an SR path.

   This document introduces the concept of Path Segment that is used to
   identify an SR path.  When used, it is inserted at the ingress node
   of the SR path and immediately follows the last segment of the SR
   path.  The Path Segment will not be popped off until it reaches the
   egress of the SR path.

   Path segment can be used by the egress node to implement path
   identification hence to support SR path PM, end-2-end SR path
   protection and bidirectional SR paths correlation.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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

Cheng, et al.            Expires January 3, 2019                [Page 1]
Internet-Draft           Path Segment in SR-MPLS               July 2018

   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 January 3, 2019.

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.  Path Segment  . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  One Label Solution  . . . . . . . . . . . . . . . . . . .   3
     2.2.  Two Labels Solution . . . . . . . . . . . . . . . . . . .   5
   3.  Path Segment Allocation . . . . . . . . . . . . . . . . . . .   6
   4.  Path Segment based PM . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Direct Packet Loss Measurement  . . . . . . . . . . . . .   7
     4.2.  Indirect Packet Loss Measurement  . . . . . . . . . . . .   7
     4.3.  Packet Delay Measurement  . . . . . . . . . . . . . . . .   8
   5.  Path Segment for Bi-directional SR Path . . . . . . . . . . .   8
   6.  Path Segment based End-2-end Path Protection  . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   9.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   9
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     11.2.  Informative References . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10
Show full document text