Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering
RFC 4874, “Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering”, is a Proposed Standard document published in April 2007 by CY. Lee, A. Farrel, S. De Cnodder. It updates RFC 3209, RFC 3473. It has since been updated by RFC 6001, RFC 8390. The canonical text is published by the RFC Editor.
Abstract
This document specifies ways to communicate route exclusions during path setup using Resource ReserVation Protocol-Traffic Engineering (RSVP-TE).
The RSVP-TE specification, "RSVP-TE: Extensions to RSVP for LSP Tunnels" (RFC 3209) and GMPLS extensions to RSVP-TE, "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions" (RFC 3473) allow abstract nodes and resources to be explicitly included in a path setup, but not to be explicitly excluded.
In some networks where precise explicit paths are not computed at the head end, it may be useful to specify and signal abstract nodes and resources that are to be explicitly excluded from routes. These exclusions may apply to the whole path, or to parts of a path between two abstract nodes specified in an explicit path. How Shared Risk Link Groups (SRLGs) can be excluded is also specified in this document. [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 4874 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4873 GMPLS Segment Recovery
- RFC 4875 Extensions to Resource Reservation Protocol - Traffic Engineering for Point-to-Multipoint TE Label Switched Paths
- RFC 4872 RSVP-TE Extensions in Support of End-to-End Generalized Multi- Protocol Label Switching Recovery
- RFC 4876 A Configuration Profile Schema for Lightweight Directory Access Protocol -Based Agents
- RFC 4871 DomainKeys Identified Mail Signatures
- RFC 4877 Mobile IPv6 Operation with IKEv2 and the Revised IPsec Architecture
- RFC 4870 Domain-Based Email Authentication Using Public Keys Advertised in the DNS
- RFC 4878 Definitions and Managed Objects for Operations, Administration, and Maintenance Functions on Ethernet-Like Interfaces