Advertisement of hierarchical and stitchable Label Switched Paths as Traffic Engineering Links
draft-shiomoto-ccamp-lsp-hierarchy-bis-01
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Kohei Shiomoto | ||
Last updated | 2006-04-26 (Latest revision 2006-03-07) | ||
Replaced by | draft-ietf-ccamp-lsp-hierarchy-bis | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-ccamp-lsp-hierarchy-bis | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document addresses topics related to hierarchical and stitched Generalized Multiprotocol Label Switching (GMPLS) Label Switched Paths (LSPs). It describes extensions to allow an egress to identify that a bi-directional LSP will be used as a dynamically signaled Forwarding Adjacency LSP (FA-LSP) or Routing Adjacency (RA). In addition, the document also addresses the issue of how to indicate that an LSP should be advertised as a traffic engineering (TE) link into a different instance of the IGP and how to identify the instance that should be used.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)