Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Authors:

JP. Vasseur, Ed.
A. Ayyangar, Ed.
R. Zhang

Stream:

IETF

Source:

ccamp (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

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

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

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

Abstract

This document specifies a per-domain path computation technique forestablishing inter-domain Traffic Engineering (TE) MultiprotocolLabel Switching (MPLS) and Generalized MPLS (GMPLS) Label SwitchedPaths (LSPs). In this document, a domain refers to a collection ofnetwork elements within a common sphere of address management or pathcomputational responsibility such as Interior Gateway Protocol (IGP)areas and Autonomous Systems.

Per-domain computation applies where the full path of an inter-domainTE LSP cannot be or is not determined at the ingress node of the TELSP, and is not signaled across domain boundaries. This is mostlikely to arise owing to TE visibility limitations. The signalingmessage indicates the destination and nodes up to the next domainboundary. It may also indicate further domain boundaries or domainidentifiers. The path through each domain, possibly including thechoice of exit point from the domain, must be determined within thedomain. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.