Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 3209,RFC 3473

Updated by:

RFC 6001,RFC 8390

Authors:

CY. Lee
A. Farrel
S. De Cnodder

Stream:

IETF

Source:

ccamp (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC4874

Discuss this RFC: Send questions or comments to the mailing listccamp@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 4874

Abstract

This document specifies ways to communicate route exclusions duringpath setup using Resource ReserVationProtocol-Traffic Engineering (RSVP-TE).

The RSVP-TE specification, "RSVP-TE: Extensions to RSVP for LSPTunnels" (RFC 3209) and GMPLS extensions to RSVP-TE, "GeneralizedMulti-Protocol Label Switching (GMPLS) Signaling Resource ReserVationProtocol-Traffic Engineering (RSVP-TE) Extensions" (RFC 3473) allowabstract nodes and resources to be explicitly included in a pathsetup, but not to be explicitly excluded.

In some networks where precise explicit paths are not computed at thehead end, it may be useful to specify and signal abstract nodes andresources that are to be explicitly excluded from routes. Theseexclusions may apply to the whole path, or to parts of a path betweentwo abstract nodes specified in an explicit path. How Shared RiskLink Groups (SRLGs) can be excluded is also specified in thisdocument. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.