IP Multicast Support in MPLS Networks
draft-acharya-ipsofacto-mpls-mcast-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Arup Acharya , Frederic Griffoul , Furquan Ansari | ||
| Last updated | 1999-02-25 | ||
| 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
Multicast support in a MPLS network has yet to be defined. This document discusses both dense-mode and sparse-mode IP multicast within the context of a MPLS network. Unlike unicast routing, dense-mode multicast routing trees are established in a data-driven manner and it is not possible to topologically aggregate such trees, which are rooted at different sources. In sparse-mode multicast, source-specific trees may coexist with a core/shared tree, and it is not possible to assign a common label to traffic from different sources on a branch of the shared tree. This leads us to suggest a per-source traffic-driven label allocation scheme for supporting all three types of multicast (dense mode, shared tree, source tree) routing trees in a MPLS network.
Authors
Arup Acharya
Frederic Griffoul
Furquan Ansari
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)