LDP Adjacency Capabilities
draft-pdutta-mpls-ldp-adj-capability-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Pranjal Dutta , Mustapha Aissaoui | ||
| Last updated | 2012-10-07 (Latest revision 2012-04-05) | ||
| 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
This document defines method for negotiation of a set of capabilities specific to a Label Distribution Protocol (LDP) Hello Adjacency. The document uses the TLVs for the LDP Capabilities defined in [RFC5561] to be used for exchanging capabilities over LDP Hello Adjacencies. The Hello Adjacency capabilities can be thought of as "Traffic Forwarding Capabilities" (TFC). Some capabilties already exist that can be re-used for hello adjacency specific capabilities and it is likely that some may be defined in future. This document defines the mechanism to advertise LDP TFCs for a hello adjacency as well as mechanism to enable and disable TFCs after a hello adjacency is formed between LDP peers.
Authors
Pranjal Dutta
Mustapha Aissaoui
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)