Required Information in Midcom Agents
draft-aoun-midcom-agent-information-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Cedric Aoun , Sanjoy Sen | ||
| Last updated | 2001-08-31 | ||
| 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
This draft is part of a gladiator contest within the MIDCOM WG to determine what network topology information is needed at the Midcom agent. By taking out application awareness from Middle Boxes in the networks, and keeping this application knowledge in the application devices (the Midcom Agents); sufficient information needs to be put in the Midcom Agent to allow them to fulfill their responsibility.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)