An End-to-End Session Layer for Realm-Specific Networking
draft-fisk-midcom-session-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mike Fisk | ||
| Last updated | 2000-11-27 | ||
| 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
Application- and transport-layer gateways are considered harmful to the Internet since they hinder the operation of existing and new end-to-end protocols. A survey of such upper-level gateways shows that they exist because of realm-specific performance, security, and protocol needs of certain portions of the Internet. Expecting this realm-specific functionality to be added manually deployted to every end hosts or application is, conversely, harmful to the flexibility of using the Internet to link disparate networks.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)