Issues surrounding a new encapsulation for IP over ATM.
draft-armitage-ipatm-encaps-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dr. Grenville Armitage , Bryan Gleeson | ||
| Last updated | 1995-06-26 (Latest revision 1995-05-24) | ||
| 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 Internet Draft draft-ietf-ipatm-ipmc-05.txt ('Support for Multicast over UNI 3.1 based ATM Networks') describes a mechanism for handling IP multicast over ATM. In doing so it notes two different mechanisms for actually achieving the multicasting of packet traffic at the ATM level. These are meshes of point to multipoint VCs, or ATM level multicast servers. If a multicast server is in use a host or router may receive a transmitted packet back on the same interface it was originally sent on. It is necessary for IP hosts and routers to be able to distinguish and discard these packets which are reflected back. This memo describes the issue in greater detail, and suggests a range of new encapsulation options.
Authors
Dr. Grenville Armitage
Bryan Gleeson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)