The Solution of Label Collision Between Multicast and Unicast
draft-huang-lable-collision-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Zheng Huang , Y. Richard Yang | ||
| Last updated | 2006-06-19 | ||
| 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
Upstream Label Suggestion and upstream label allocation schemes are introduced and simply defined in [OVER][UPSTREAM]. But it is possible that the same label will be allocated for unicast LSP and multicast LSP on the same link. In upstream label allocation, it solves the collision through layer 2 encapsulation and context-specific label space. But in the Upstream Label Suggestion allocation scheme, the collision can not be solved if downstream LSRs do not support context-specific label space. This document details the solution of label collision between multicast and unicast for the Upstream Label Suggestion allocation scheme.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)