Implications of NATs on the TCP/IP architecture
draft-ietf-nat-arch-implications-00
| Document | Type |
Expired Internet-Draft
(nat WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Yakov Rekhter | ||
| Last updated | 1998-08-07 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
In light of the growing interest in, and deployment of network address translation (NAT - RFC 1631), this document will present some highlights of the architectural implications. A reader is assumed to be well familiar with the principles of NAT operations [RFC1631].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)