<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-spring-mpls-path-segment" target="https://datatracker.ietf.org/doc/html/draft-ietf-spring-mpls-path-segment-17">
   <front>
      <title>Path Segment in MPLS Based Segment Routing Network</title>
      <author initials="W." surname="Cheng" fullname="Weiqiang Cheng">
         <organization>China Mobile</organization>
      </author>
      <author initials="H." surname="Li" fullname="Han Li">
         <organization>China Mobile</organization>
      </author>
      <author initials="C." surname="Li" fullname="Cheng Li">
         <organization>Huawei Technologies Co., Ltd</organization>
      </author>
      <author initials="R." surname="Gandhi" fullname="Rakesh Gandhi">
         <organization>Cisco Systems, Inc.</organization>
      </author>
      <author initials="R." surname="Zigler" fullname="Royi Zigler">
         <organization>Broadcom</organization>
      </author>
      <date month="November" day="16" year="2023" />
      <abstract>
	 <t>   A Segment Routing (SR) path is identified by an SR segment list.  A
   sub-set of segments from the segment list cannot distinguish one SR
   path from another as they may be partially congruent.  SR path
   identification is a pre-requisite for various use-cases such as
   Performance Measurement (PM), and end-to-end 1+1 path protection.

   In SR for MPLS data plane (SR-MPLS), an Egress node cannot determine
   on which SR path a packet traversed the network from the label stack
   because the segment identifiers are removed from the label stack as
   the packet transits the network.

   This document defines Path Segment to identify an SR path on the
   egress node of the path.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-spring-mpls-path-segment-17" />
   
</reference>
