Application Considerations for Midcom Middleboxes
draft-shore-midcom-apps-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Melinda Shore | ||
| Last updated | 2001-05-11 | ||
| 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
As an architecture is evolving around an interface between middleboxes in the transport plane [Srisuresh] and the applications which must traverse them, we need to document the implications for applications. This documentation is intended both to provide guidance for application designers and to help network architects come to a better understanding of sources of complexity in our networks.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)