Skip to main content

Label Switched Paths (LSP) Hierarchy with Generalized Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE)
RFC 4206

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'To improve scalability of Generalized Multi-Protocol Label Switching (GMPLS) it may be useful to aggregate Label …
Received changes through RFC Editor sync (changed abstract to 'To improve scalability of Generalized Multi-Protocol Label Switching (GMPLS) it may be useful to aggregate Label Switched Paths (LSPs) by creating a hierarchy of such LSPs. A way to create such a hierarchy is by (a) a Label Switching Router (LSR) creating a Traffic Engineering Label Switched Path (TE LSP), (b) the LSR forming a forwarding adjacency (FA) out of that LSP (by advertising this LSP as a Traffic Engineering (TE) link into the same instance of ISIS/OSPF as the one that was used to create the LSP), (c) allowing other LSRs to use FAs for their path computation, and (d) nesting of LSPs originated by other LSRs into that LSP (by using the label stack construct).

This document describes the mechanisms to accomplish this. [PROPOSED STANDARD]')
2015-10-14
(System) Notify list changed from ,  to (None)
2005-10-31
(System) Last call text was added
2005-10-31
Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2005-10-31
Amy Vezza [Note]: 'RFC 4206' added by Amy Vezza
2005-10-27
(System) RFC published