Interworking between IP VPN and shared backbone multicast domains
draft-celer-vpn-mcast-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Alicja B. Celer | ||
| Last updated | 2000-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
This draft introduces an interworking function between shared backbone multicast domain and VPN multicast domain. The architecture that follows is similar to Multicast Border Router functionality, however the mapping is defined not as a mapping between two different multicast protocols, but two different multicast topologies the under assumption that the shared backbone multicast topology will be shared between VPNs for carrying the traffic. The main assumption made in this draft is that multicast packets are replicated on PE device (router) for scalability and performance reasons. However, it is possible to extend the solution and replicate packets on CE devices. The proposed mapping of addresses to topology solves the issue of scalability of multicast addresses to state knowledge in the core. This draft also identifies three types of multicast capabilities for the core.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)