%% You should probably cite draft-arora-mpls-spring-ttl-procedures-srte-paths-01 instead of this revision. @techreport{arora-mpls-spring-ttl-procedures-srte-paths-00, number = {draft-arora-mpls-spring-ttl-procedures-srte-paths-00}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-arora-mpls-spring-ttl-procedures-srte-paths/00/}, author = {Kapil Arora and Shraddha Hegde}, title = {{TTL Procedures for SR-TE Paths in Label Switched Path Traceroute Mechanisms}}, pagetotal = 8, year = , month = , day = , abstract = {Segment routing supports the creation of explicit paths using adjacency-sids, node-sids, and anycast-sids. The SR-TE paths are built by stacking the labels that represent the nodes and links in the explicit path. A very useful Operations And Maintenance requirement is to be able to trace these paths as defined in {[}RFC8029{]}. This document specifies a uniform mechanism to support MPLS traceroute for the SR-TE paths when the nodes in the network are following uniform mode or short-pipe mode {[}RFC3443{]}.}, }