IP Architecture Extensions for ATM
draft-rekhter-ip-atm-architecture-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Yakov Rekhter | ||
| Last updated | 1995-07-06 (Latest revision 1995-01-25) | ||
| 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 original IP architecture assumes that each Data Link subnetwork is labeled with a single IP network number. As indicated in RFC1620, this assumption may be violated for large data networks, including ATM-based networks. The architecture works even when this assumption is violated, but it imposes constraints on communication among hosts and routers through an ATM-based network, which in turn may preclude full utilization of ATM capabilities. This document describes extensions to the IP architecture that relaxes these constraints, thus enabling the full utilization of the services provided by ATM.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)