Skip to main content

Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)
RFC 4874

Revision differences

Document history

Date By Action
2020-01-21
(System) Received changes through RFC Editor sync (added Verified Errata tag)
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'This document specifies ways to communicate route exclusions during path setup using Resource ReserVation Protocol-Traffic Engineering …
Received changes through RFC Editor sync (changed abstract to '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]')
2017-05-16
(System) Changed document authors from "Adrian Farrel, Stefaan De Cnodder" to "Adrian Farrel, Stefaan De Cnodder, Cheng-Yin Lee"
2015-10-14
(System) Notify list changed from ccamp-chairs@ietf.org to (None)
2007-04-16
Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2007-04-16
Amy Vezza [Note]: 'RFC 4874' added by Amy Vezza
2007-04-10
(System) RFC published