%% You should probably cite draft-ietf-idr-bgp-sr-segtypes-ext or draft-ietf-idr-sr-policy-safi instead of this I-D. @techreport{ietf-idr-segment-routing-te-policy-10, number = {draft-ietf-idr-segment-routing-te-policy-10}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-idr-segment-routing-te-policy/10/}, author = {Stefano Previdi and Clarence Filsfils and Ketan Talaulikar and Paul Mattes and Eric C. Rosen and Dhanendra Jain and Steven Lin}, title = {{Advertising Segment Routing Policies in BGP}}, pagetotal = 47, year = , month = , day = , abstract = {This document defines a new BGP SAFI with a new NLRI in order to advertise a candidate path of a Segment Routing (SR) Policy. An SR Policy is a set of candidate paths, each consisting of one or more segment lists. The headend of an SR Policy may learn multiple candidate paths for an SR Policy. Candidate paths may be learned via a number of different mechanisms, e.g., CLI, NetConf, PCEP, or BGP. This document specifies the way in which BGP may be used to distribute SR Policy candidate paths. New sub-TLVs for the Tunnel Encapsulation Attribute are defined for signaling information about these candidate paths.}, }