MAPEX Application level multicast architectural requirements for APEX
draft-crowcroft-apex-multicast-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jon Crowcroft , Ken Carlberg | ||
| Last updated | 2001-10-02 | ||
| 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
This is a memo that presents an approach to do application layer multicast. Our intention is to present a design that produces a tree distribution structure within the existing design structure of APEX and BEEP. It is not our intention to present a design that replaces multicast at the network layer. Where the need exists (and in scenarios where it would seem symbiotic), we would find it constructive to integrate the two technologies and perspective (i.e., application later and network layer multicast).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)