A Middle Box Architectural Framework
draft-lear-middlebox-arch-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Eliot Lear | ||
Last updated | 2001-02-01 | ||
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 used to be reasonable to expect that any two points connected to the Internet to have the ability to hold any communication. Such an expectation has not be reasonable for quite some time, thanks to firewalls, NATs, and other intermediate devices. Today, we acknowledge a new architecture and we name the functional blocks of that architecture as well as several ways to get ends to communicate, and how two devices could expect to communicate with each other. This document does not define the protocols involved.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)