MPLS Multicast Traffic Engineering
draft-ooms-mpls-multicast-te-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dirk Ooms | ||
| Last updated | 2002-03-01 | ||
| 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
There are several reasons for operators to construct multicast trees by another means than multicast routing protocols. This document lists these reasons and describes 2 ways of building a multicast traffic-engineered tree: root-initiated tree and leaf-initiated tree. Finally it defines extensions to CR-LDP to support MPLS multicast traffic engineering.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)