@techreport{wang-idr-sr-policy-pce-delegation-00,
    number =    {draft-wang-idr-sr-policy-pce-delegation-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-wang-idr-sr-policy-pce-delegation/00/},
    author =    {Yang Wang and Hao Li and Yuanxiang Qiu and Liping Yang and Mengxiao Chen},
    title =     {{Segment Routing PCE Delegation in BGP}},
    pagetotal = 10,
    year =      2021,
    month =     feb,
    day =       2,
    abstract =  {Segment Routing is a source routing paradigm that explicitly indicates the forwarding path for packets at the ingress node. An SR policy is a set of candidate SR paths consisting of one or more segment lists with necessary path attributes. 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. The Path Computation Element (PCE) provides path computation functions in support of traffic engineering in Multi Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. Currently, when a controller uses BGP to deploy an SR Policy, there is no way to encode PCE delegation related options. The only way to import a PCE delegation is through local configuration management, e.g., Netconf, CLI or gRPC. This document defines extensions to BGP to distribute PCE delegation information within an SR policy.},
}