A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 21
- Abstract
- This document specifies a per-domain path computation technique for establishing inter-domain Traffic Engineering (TE) Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Label Switched Paths (LSPs). In this document, a domain refers to a collection of network elements within a common sphere of address management or path computational responsibility such as Interior Gateway Protocol (IGP) areas and Autonomous Systems. Per-domain computation applies where the full path of an inter-domain TE LSP cannot be or is not determined at the ingress node of the TE LSP, and is not signaled across domain boundaries. This is most likely to arise owing to TE visibility limitations. The signaling message indicates the destination and nodes up to the next domain boundary. It may also indicate further domain boundaries or domain identifiers. The path through each domain, possibly including the choice of exit point from the domain, must be determined within the domain. [STANDARDS-TRACK]
- Publication Date
- 2008-02-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC5152- Link
- https://doi.org/10.17487/RFC5152
- Author(s)
- JP VasseurArthi AyyangarRaymond Zhang
- Keyword(s)
- MPLS, GMPLS
Latest version of IETF RFC 5152
Document Versions — IETF RFC 5152
-
▶ IETF RFC 5152 (2008-02-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 3209 [Active*]
- IETF RFC 3473 [Active*]
Bibliographic Reference(s)
- IETF RFC 2702 [Active*]
- IETF RFC 2747 [Active*]
- IETF RFC 3097 [Active*]
- IETF RFC 3630 [Active*]
- IETF RFC 3784 [Superseded*]
- IETF RFC 4090 [Active*]
- IETF RFC 4105 [Active*]
- IETF RFC 4203 [Active*]
- IETF RFC 4205 [Superseded*]
- IETF RFC 4216 [Active*]
- IETF RFC 4655 [Active*]
- IETF RFC 4726 [Active*]
- IETF RFC 4736 [Active*]
- IETF RFC 4920 [Active*]
- IETF RFC 5150 [Active*]
- IETF RFC 5151 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5152.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5152, A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs). Available at https://doi.org/10.17487/RFC5152
Snippet:
IETF RFC 5152, A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs). Available at https://doi.org/10.17487/RFC5152
HTML (ISO 690 compliant)
Preview:
IETF RFC 5152, A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs). Available at https://doi.org/10.17487/RFC5152
Snippet:
<span class="citation"><cite>IETF RFC 5152</cite>, A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs). Available at <a href="https://doi.org/10.17487/RFC5152" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5152</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5152, A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs)
doi: 10.17487/RFC5152
url: https://doi.org/10.17487/RFC5152
doi: 10.17487/RFC5152
url: https://doi.org/10.17487/RFC5152
Snippet:
<li> <cite id="bib-rfc5152">IETF RFC 5152</cite>, A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs) <span class="doi">10.17487/RFC5152</span> </li>
Referenced By
- IETF RFC 5150 [Active*]
- IETF RFC 5151 [Active*]
- IETF RFC 5298 [Active*]
- IETF RFC 5316 [Superseded*]
- IETF RFC 5376 [Active*]
- IETF RFC 5392 [Active*]
- IETF RFC 5441 [Active*]
- IETF RFC 5520 [Active*]
- IETF RFC 5521 [Active*]
- IETF RFC 6601 [Active*]
- IETF RFC 6805 [Active*]
- IETF RFC 7752 [Superseded*]
- IETF RFC 9552 [Active*]