@misc{rfc8426,
    series =    {Request for Comments},
    number =    8426,
    howpublished =  {RFC 8426},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC8426},
    url =       {https://www.rfc-editor.org/info/rfc8426},
    author =    {Harish Sitaraman and Vishnu Pavan Beeram and Ina Minei and Siva Sivabalan},
    title =     {{Recommendations for RSVP-TE and Segment Routing (SR) Label Switched Path (LSP) Coexistence}},
    pagetotal = 12,
    year =      2018,
    month =     jul,
    abstract =  {Operators are looking to introduce services over Segment Routing (SR) Label Switched Paths (LSPs) in networks running Resource Reservation Protocol - Traffic Engineering (RSVP-TE) LSPs. In some instances, operators are also migrating existing services from RSVP-TE to SR LSPs. For example, there might be certain services that are well suited for SR and need to coexist with RSVP-TE in the same network. Such introduction or migration of traffic to SR might require coexistence with RSVP-TE in the same network for an extended period of time, depending on the operator's intent. The following document provides solution options for keeping the traffic engineering database consistent across the network, accounting for the different bandwidth utilization between SR and RSVP-TE.},
}