Talking to Stuff In The Network: Middlebox Communication Models
draft-shore-midcom-protos-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Melinda Shore | ||
| Last updated | 2003-10-21 | ||
| 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
It is increasingly common for applications to want to influence the behavior of equipment in the network, in violation of various tenets underpinning the the design of IP. A number of different mechanisms and architectures have been proposed, and this very drafty draft is a hoped to be a start at discussing some of the issues related to protocols used for middlebox communication.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)