RFC 2663: IP Network Address Translator (NAT) Terminology and Considerations
In plain English — editorial summary, not part of the RFC
This document attempts to describe the operation of NAT devices and the associated considerations in general, and to define the terminology used to identify various flavors of NAT. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2663
- Published
- August 1999
- Authors
- P. Srisuresh; M. Holdrege
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2709Security Model with Tunnel-mode IPsec for NAT DomainsCurrent
October 1999
- RFC 2529Transmission of IPv6 over IPv4 Domains without Explicit TunnelsCurrent
March 1999
- RFC 2746RSVP Operation Over IP TunnelsCurrent
January 2000
- RFC 2475An Architecture for Differentiated ServicesUpdated
December 1998
- RFC 3027Protocol Complications with the IP Network Address TranslatorCurrent
January 2001
- RFC 3242RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTPObsoleted
April 2002
- RFC 3453The Use of Forward Error Correction (FEC) in Reliable MulticastCurrent
December 2002
- RFC 3738Wave and Equation Based Rate Control (WEBRC) Building BlockCurrent
April 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?