Requirements for multicast service using a group label over MPLS
draft-choi-mpls-grouplabel-requirement-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jun Kyun Choi | ||
| Last updated | 2003-10-23 | ||
| 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
As the group communication become more important, the special label should be allocated in support of group management and maintenance. The allocation mechanism of a group label can be applied to a point- to-multipoint(P2MP) communication in MPLS networks. Currently used label is locally significant, while this group label should be common object within a single MPLS domain. This document presents a set of requirements for multicast service using a group label over Multiprotocol Label Switching(MPLS). It identifies functional and performance capabilities required to allocate a group label in master-slave network and peer to peer network, which facilitates efficient and reliable group communication and Quality of Service(QoS) in MPLS domain. It also identifies functional capabilities required to implement several services related to Content Distribution Network(CDN) in master-slave network.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)