Using LDP Multipoint Extensions on Targeted LDP Sessions
draft-napierala-mpls-targeted-mldp-03
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Maria Napierala , Eric C. Rosen | ||
| Last updated | 2012-10-10 (Latest revision 2012-04-20) | ||
| Replaced by | draft-ietf-mpls-targeted-mldp | ||
| 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-mpls-targeted-mldp | |
| 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
Label Distribution Protocol (LDP) can be used to set up Point-to-Multipoint (P2MP) and Multipoint-to-Multipoint (MP2MP) Label Switched Paths. The existing specification for this functionality assumes that a pair of LDP neighbors are directly connected. However, the LDP base specification allows for the case where a pair of LDP neighbors are not directly connected; the LDP session between such a pair of neighbors is known as a "Targeted LDP" session. This document specifies the use of the LDP P2MP/MP2MP extensions over a Targeted LDP session.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)