Skip to main content

Recommendations for RSVP-TE and Segment Routing (SR) Label Switched Path (LSP) Coexistence
RFC 8426

Revision differences

Document history

Date By Action
2018-07-30
(System)
Received changes through RFC Editor sync (created alias RFC 8426, changed title to 'Recommendations for RSVP-TE and Segment Routing (SR) Label Switched Path (LSP) …
Received changes through RFC Editor sync (created alias RFC 8426, changed title to 'Recommendations for RSVP-TE and Segment Routing (SR) Label Switched Path (LSP) Coexistence', changed abstract to '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.', changed standardization level to Informational, changed state to RFC, added RFC published event at 2018-07-30, changed IESG state to RFC Published)
2018-07-30
(System) RFC published