MVPN: Using Bidirectional P-Tunnels
draft-rosen-l3vpn-mvpn-bidir-03
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Arjen Boers , Yiqun Cai , Eric C. Rosen , IJsbrand Wijnands | ||
| Last updated | 2011-11-01 (Latest revision 2011-02-01) | ||
| Replaced by | draft-ietf-l3vpn-mvpn-bidir | ||
| 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-bidir | |
| 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
The documents specifying multicast support for BGP/MPLS IP VPNs allow customer multicast data to be transported through a service provider's network through a set multicast tunnels. Such tunnels are advertised by BGP in a BGP attribute known as the "Provider Multicast Service Interface (PMSI) Tunnel Attribute". The base specifications allow the PMSI Tunnel Attribute to advertise bidirectional multicast distribution trees as "PMSI Tunnels"; however, those documents do not provide all the necessary details for using those tunnels. These details are provided in this document. This document also specifies the procedures for assigning customer multicast flows to specific bidirectional PMSI tunnels.
Authors
Arjen Boers
Yiqun Cai
Eric C. Rosen
IJsbrand Wijnands
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)