RFC - 3022
Traditional IP Network Address Translator (Traditional NAT)
| Original: | ftp://ftp.isi.edu/in-notes/rfc3022.txt |
|---|---|
| Authors: | P. Srisuresh [Jasmine Networks], K. Egevang [Intel Corporation] |
| Date: | January 2001 |
| Category: | Informational |
| Obsoletes: | |
|---|---|
| RFC-1631 | The IP Network Address Translator (NAT) (Obsoleted by RFC-3022) |
| Referred by: | 21 RFC |
| Refers to: | 11 RFC |
Status
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved.
Abstract
Preface
The NAT operation described in this document extends address translation introduced in RFC 1631(-> 3022) and includes a new type of network address and TCP/UDP port translation. In addition, this document corrects the Checksum adjustment algorithm published in RFC 1631(-> 3022) and attempts to discuss NAT operation and limitations in detail.
Abstract
Basic Network Address Translation or Basic NAT is a method by which IP addresses are mapped from one group to another, transparent to end users. Network Address Port Translation, or NAPT is a method by which many network addresses and their TCP/UDP (Transmission Control Protocol/User Datagram Protocol) ports are translated into a single network address and its TCP/UDP ports. Together, these two operations, referred to as traditional NAT, provide a mechanism to connect a realm with private addresses to an external realm with globally unique registered addresses.
-
prepared by Miloslav Nic
- the founder of Zvon.org and Law-Ref.org
- the head of B.Sc. program Informatics and chemistry [in Czech]
- the founder of Lidem.org - Volby 2006 - parliamentary elections in the Czech Republic [in Czech]
- the chief consultant of the publishing house ICT Press
- and Pavel Srb, a student of B.Sc. program Informatics and chemistry
