Middle Box discovery integration solutions within the Midcom architecture
draft-aoun-middlebox-discovery-comparison-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Cedric Aoun | ||
| Last updated | 2002-06-26 | ||
| 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
Middle Box discovery is one of the problems that the Midcom architecture has not yet solved. This document compares two Middle box discovery solutions: The decoupled model where the Middle Box discovery is handled by a separate protocol than the MIDCOM protocol vs the combo model were the MIDCOM protocol and the discovery protocol are the same.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)