Congruency for VPLS Multicast and Unicast Paths
draft-sajassi-l2vpn-vpls-multicast-congruency-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Ali Sajassi | ||
| Last updated | 2005-11-17 | ||
| 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 current VPLS multicast proposals based on multicast tree has several issues that are outlined in [BRIDGE-INTEROP]. These issues stems from the divergence of the multicast and unicast paths for a given VPLS instance in the MPLS/IP network. This draft describes a mechanism for building multicast and unicast paths that are congruent in order to address these issues.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)