Partitioning Tag Space among Multicast Routers on a Common Subnet
draft-farinacci-multicast-tag-part-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dino Farinacci | ||
| Last updated | 1996-12-16 | ||
| 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 tagswitching. 1) Tag Allocation, which requires each multicast Tag Switching Router (TSR) to have a tag value range that it uses. 2) Tag Binding, using the tags allocated, a TSR must assign them to multicast routes. 3) Tag Binding Distribution, after binding tag values to routes, they must be distributed to other TSRs so they all forward on a common and consistent distribution tree. In this document we present how tags are allocated uniquely across multicast capable TSRs 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.)