Propagation of VPLS IP Multicast Group Membership Information
draft-raggarwa-l2vpn-vpls-mcast-ctrl-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Rahul Aggarwal | ||
| Last updated | 2005-07-12 | ||
| 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
The PEs participating in VPLS need to learn the IP multicast group membership information from remote VPLS sites to enable them to send an IP multicast packet to only those other PEs in the VPLS that have receivers interested in that particular IP multicast packet's multicast source and group. This document describes procedures for propagating multicast control information, learned from local Virtual Private LAN Service (VPLS) sites, to remote VPLS sites. IGMP or PIM snooping is required only on the customer facing interfaces. The procedures do not require IGMP or PIM snooping on the Service Provider backbone links. Instead they use reliable protocol messages to exchange multicast control information between the PEs.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)