GMPLS Extensions for Dynamic Trunking
draft-cheng-gmpls-dynamic-trunking-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dean Cheng | ||
| Last updated | 2001-06-19 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
Currently the GMPLS signaling requires to include a 'LSP Encoding Type' in the Generalized Label Request ([GMPLS-SIG]), which indicates the encoding of the LSP being requested. Upon receiving a RSVP PATH message or CR-LDP REQUEST message that contains a Generalized Label Request, a LSR must verify if the receiving and transmitting interface can support the LSP. In particular on the transmitting side, the node either finds an interface that has the same switching class, among other requirements, or it may use a FA-LSP, i.e., another class of switching.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)