Controlling the number of egress points in dynamic multicast groups
draft-leecy-multicast-egress-limit-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Cheng-Yin Lee , Nabil Seddigh | ||
| Last updated | 1999-10-27 | ||
| 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
The amount of resources required by a source to send data to a multicast group within a network is dependent on the service level the source requested and the number of egress points for the group in a network. Since the egress points in a multicast group can change during a multicast session, a source node would not know how many or which egress points it would be sending to when it specifies the service level it requires for multicast data. This document describes methods to control the number of egress points of a dynamic multicast group in a differentiated services (DS) network. A source node specifies the bandwidth, type of service and a limit on the number of egress points that it wants to send multicast data to. If this limit on the number of egress points is reached, no further egress points will be grafted to the branch of the multicast tree rooted at this source node.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)