Network topology considerations in the MIDCOM Architectural framework
draft-aoun-midcom-network-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Cedric Aoun | ||
| Last updated | 2001-06-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
In the present Internet architecture, packet transparency is lost due to the introduction of Middle Boxes that either modifies the contents of the IP packet, or drops it (Ref [RFC2775]). This draft presents in the context of the MIDCOM workgroup framework several Middle Boxes network deployment scenarios that needs to be considered.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)