Skip to main content

A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs)
RFC 5152

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'This document specifies a per-domain path computation technique for establishing inter-domain Traffic Engineering (TE) Multiprotocol Label …
Received changes through RFC Editor sync (changed abstract to '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]')
2017-05-16
(System) Changed document authors from "Raymond Zhang, Arthi Ayyangar" to "Raymond Zhang, Arthi Ayyangar, JP Vasseur"
2015-10-14
(System) Notify list changed from ccamp-chairs@ietf.org to (None)
2008-03-25
Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2008-03-25
Amy Vezza [Note]: 'RFC 5152' added by Amy Vezza
2008-02-28
(System) RFC published