LDP IP and PW Capability
draft-raza-mpls-ldp-ip-pw-capability-01
| Document | Type |
Replaced Internet-Draft
(mpls WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Syed Kamran Raza , Sami Boutros | ||
| Last updated | 2011-06-17 (Latest revision 2011-04-20) | ||
| Replaced by | draft-ietf-mpls-ldp-ip-pw-capability | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-mpls-ldp-ip-pw-capability | |
| Consensus boilerplate | Unknown | ||
| 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, no LDP capability is exchanged for LDP applications like IP label switching and L2VPN/PW signaling. When an LDP session comes up, an LDP speaker may unnecessarily advertise its local state for such LDP applications even when the peer session may be established for some other applications like ICCP. This document proposes a solution by which an LDP speaker announces its "incapability" or disability or non-support for IP label switching or L2VPN/PW application, hence disabling corresponding application state exchange over the established LDP session.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)