Integrated Servces IP Multicasting over ATM
draft-milliken-ipatm-services-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Walter Milliken | ||
| Last updated | 1995-07-07 | ||
| 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 paper describes an integrated services approach to supporting IP multicast over ATM, including both best-effort delivery and quality of service-based (QoS) traffic. Best-effort traffic is assumed to be relatively low-volume and short-duration sessions, and thus should not incur ATM VC setup overhead. QoS-based traffic is assumed to be high-volume, long-duration sessions, and ATM VC setup is thus both desirable and necessary (to support quality of service demands). Best-effort traffic delivery is based on standard IGMP and IP multicast routing. QoS support is provided by use of RSVP. Various types of 'short-cut' ATM VC setup can be supported by minor changes to router behavior and the RSVP protocol.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)