GMPLS Segment Recovery
RFC 4873, “GMPLS Segment Recovery”, is a Proposed Standard document published in May 2007 by L. Berger, I. Bryskin, D. Papadimitriou, A. Farrel. It updates RFC 3473, RFC 4872. It has since been updated by RFC 9270. The canonical text is published by the RFC Editor.
Abstract
This document describes protocol specific procedures for GMPLS (Generalized Multi-Protocol Label Switching) RSVP-TE (Resource ReserVation Protocol - Traffic Engineering) signaling extensions to support label switched path (LSP) segment protection and restoration. These extensions are intended to complement and be consistent with the RSVP-TE Extensions for End-to-End GMPLS Recovery (RFC 4872). Implications and interactions with fast reroute are also addressed. This document also updates the handling of NOTIFY_REQUEST objects. [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 4873 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4872 RSVP-TE Extensions in Support of End-to-End Generalized Multi- Protocol Label Switching Recovery
- RFC 4874 Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering
- RFC 4871 DomainKeys Identified Mail Signatures
- RFC 4875 Extensions to Resource Reservation Protocol - Traffic Engineering for Point-to-Multipoint TE Label Switched Paths
- RFC 4870 Domain-Based Email Authentication Using Public Keys Advertised in the DNS
- RFC 4876 A Configuration Profile Schema for Lightweight Directory Access Protocol -Based Agents
- RFC 4869 Suite B Cryptographic Suites for IPsec
- RFC 4877 Mobile IPv6 Operation with IKEv2 and the Revised IPsec Architecture