Encoding mLDP FECs in the NLRI of BGP MCAST-VPN Routes
draft-rosen-l3vpn-mvpn-mldp-nlri-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | IJsbrand Wijnands , Eric C. Rosen , Uwe Joorde | ||
| Last updated | 2013-10-14 (Latest revision 2012-08-20) | ||
| Replaced by | RFC 7441 | ||
| 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-l3vpn-mvpn-mldp-nlri | |
| 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
Many service providers offer "BGP/MPLS IP VPN" service to their customers. Existing IETF standards specify the procedures and protocols that a service provider uses in order to offer this service to customers who have IP unicast and IP multicast traffic in their VPNs. It is also desirable to be able to support customers who have MPLS multicast traffic in their VPNs. This document specifies the procedures and protocol extensions that are needed to support customers who use the Multicast Extensions to Label Distribution Protocol (mLDP) as the control protocol for their MPLS multicast traffic. Existing standards do provide some support for customers who use mLDP, but only under a restrictive set of circumstances. This document generalizes the existing support to include all cases where the customer uses mLDP, without any restrictions.
Authors
IJsbrand Wijnands
Eric C. Rosen
Uwe Joorde
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)