MPLS Traffic Engineering Soft Preemption
RFC 5712, “MPLS Traffic Engineering Soft Preemption”, is a Proposed Standard document published in January 2010 by M. Meyer, JP. Vasseur. The canonical text is published by the RFC Editor.
Abstract
This document specifies Multiprotocol Label Switching (MPLS) Traffic Engineering Soft Preemption, a suite of protocol modifications extending the concept of preemption with the goal of reducing or eliminating traffic disruption of preempted Traffic Engineering Label Switched Paths (TE LSPs). Initially, MPLS RSVP-TE was defined with support for only immediate TE LSP displacement upon preemption. The utilization of a reroute request notification helps more gracefully mitigate the reroute process of preempted TE LSP. For the brief period soft preemption is activated, reservations (though not necessarily traffic levels) are in effect under-provisioned until the TE LSP(s) can be rerouted. For this reason, the feature is primarily, but not exclusively, interesting in MPLS-enabled IP networks with Differentiated Services and Traffic Engineering capabilities. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5712 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5711 Node Behavior upon Originating and Receiving Resource Reservation Protocol Path Error Messages
- RFC 5713 Security Threats and Security Requirements for the Access Node Control Protocol
- RFC 5710 PathErr Message Triggered MPLS and GMPLS LSP Reroutes
- RFC 5714 IP Fast Reroute Framework
- RFC 5715 A Framework for Loop-Free Convergence
- RFC 5708 X.509 Key and Signature Encoding for the KeyNote Trust Management System
- RFC 5716 Requirements for Federated File Systems
- RFC 5707 Media Server Markup Language