Partitioning Label Space among Multicast Routers on a Common Subnet
draft-farinacci-multicast-label-part-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dino Farinacci , Yakov Rekhter | ||
| Last updated | 1999-08-31 | ||
| 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 3 major functions that must be performed to achieve multicast Label Switching. 1) Label Allocation, which requires each multicast Label Switching Router (LSR) to have a label value range that it uses. 2) Label Binding, using the labels allocated, a LSR must assign them to multicast routes. 3) Label Binding Distribution, after binding label values to routes, they must be distributed to other LSRs so they all forward on a common and consistent distribution tree. In this document we present how labels are allocated uniquely across multicast capable LSRs on a LAN and point-to-point IP subnets.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)