Establishing Reachability Behind NATs
draft-shore-nat-reachability-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Melinda Shore | ||
| Last updated | 2004-03-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
One of the most persistent, difficult problems introduced with NATs is voluntary reachability -- a NATted device making itself avail- able to the public internet. This paper is an overview of the cur- rent status of reachability, a decomposition of the problem and a proposal for going forward.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)