Multicast Servers in an RFC 1577 Environment.
draft-armitage-ipatm-mcserv-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. Grenville Armitage | ||
| Last updated | 1994-11-04 | ||
| 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
In some environments the consumption of reassembly contexts and VC space may be too high for all Class D groups to use full VC meshes as described in Internet Draft draft-armitage-ipatm-ipmc-02.txt ('IP Multicast over UNI 3.0 based ATM Networks'). This memo explores possible ways of sharing the load between Multicast Servers and full VC meshes in an RFC 1577/UNI3.0 environment.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)