Extending NAT
draft-rfced-info-hurn-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mike Hurn | ||
| Last updated | 1996-08-07 (Latest revision 1996-01-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
This document describes how the addressing scheme of the 'IP Network Address Translator (NAT) [1] could be extended. The extension takes advantage of the fact that the source port number in a full TCP/IP packet can be any value the originating host is not currently using. It also exploits the fact that (nearly) all the networking software will work with DNS. By using DNS and proxies the ENAT systems perform the address translation indirectly. For convenience the term ENAT will be used for the extended addressing scheme to distinguish it from the original. A ENAT system could be used equally for UDP/IP as well as TCP/IP. ICMP can be handled with restrictions.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)