A Method for the Transmission of Internet Packets Over AppleTalk Networks [MacIP]
draft-ietf-appleip-MacIP-02
| Document | Type |
Expired Internet-Draft
(appleip WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tom Evans , Christopher S. Ranch | ||
| Last updated | 1992-11-12 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 Internet Draft describes an existing protocol for transporting IP packets over AppleTalk networks. It is intended to specify, standardize, and enhance existing implementations. There is much confusion over what MacIP really is, as it has grown by many small increments designed and implemented by at least as many people. There has been no central or formal design document, so each of the protocol additions and their effects are not well understood. We hope to dissect the anatomy of the current state of the art, and recommend a functional subset of the protocol features and a new gateway architecture that will help provide services to multiple zones more reliably. The MacIP protocol is used to transport IP packets across AppleTalk networks. There are many existing host and gateway implementations of this protocol, and most of them have many slight differences.
Authors
Tom Evans
Christopher S. Ranch
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)