@misc{rfc8669,
    series =    {Request for Comments},
    number =    8669,
    howpublished =  {RFC 8669},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC8669},
    url =       {https://www.rfc-editor.org/info/rfc8669},
    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 =      2019,
    month =     dec,
    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.},
}