%% You should probably cite rfc8669 instead of this I-D. @techreport{ietf-idr-bgp-prefix-sid-27, number = {draft-ietf-idr-bgp-prefix-sid-27}, 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-bgp-prefix-sid/27/}, author = {Stefano Previdi and Clarence Filsfils and Acee Lindem and Arjun Sreekantiah and Hannes Gredler}, title = {{Segment Routing Prefix Segment Identifier Extensions for BGP}}, pagetotal = 15, year = 2018, month = jun, day = 26, abstract = {Segment Routing (SR) leverages the source-routing paradigm. A node steers a packet through an ordered list of instructions called "segments". A segment can represent any instruction, topological or service based. The ingress node prepends an SR header to a packet containing a set of segment identifiers (SIDs). Each SID represents a topological or service-based instruction. Per-flow state is maintained only on the ingress node of the SR domain. An "SR domain" is defined as a single administrative domain for global SID assignment. This document defines an optional, transitive BGP attribute for announcing information about BGP Prefix Segment Identifiers (BGP Prefix-SIDs) and the specification for SR-MPLS SIDs.}, }