Recommendations for RSVP-TE and Segment Routing Label Switched Path Coexistence
RFC 8426, “Recommendations for RSVP-TE and Segment Routing Label Switched Path Coexistence”, is an Informational document published in July 2018 by H. Sitaraman, V. Beeram, I. Minei, S. Sivabalan. The canonical text is published by the RFC Editor.
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 8426 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8425 IANA Considerations for IPv6 Neighbor Discovery Prefix Information Option Flags
- RFC 8427 Representing DNS Messages in JSON
- RFC 8424 Extensions to RSVP-TE for Label Switched Path Ingress Fast Reroute Protection
- RFC 8428 Sensor Measurement Lists
- RFC 8423 Reclassification of Suite B Documents to Historic Status
- RFC 8429 Deprecate Triple-DES and RC4 in Kerberos
- RFC 8422 Elliptic Curve Cryptography Cipher Suites for Transport Layer Security Versions 1.2 and Earlier
- RFC 8430 RIB Information Model