Multicast in BGP/MPLS VPNs and VPLS
draft-raggarwa-l3vpn-mvpn-vpls-mcast-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Rahul Aggarwal | ||
| Last updated | 2004-10-28 | ||
| 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 describes a solution framework for overcoming the limitations of existing Multicast VPN (MVPN) and VPLS multicast solutions. It describes procedures for enhancing the scalability of multicast for BGP/MPLS VPNs. It also describes procedures for VPLS multicast that utilize multicast trees in the sevice provider (SP) network. The procedures described here reduce the overhead of PIM neighbor relationships that a PE router needs to maintain for BGP/MPLS VPNs. They also reduce the state (and the overhead of maintaining the state) in the SP network by removing the need to maintain in the SP network at least one dedicated multicast tree per each VPN.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)