RFC 2993: Architectural Implications of NAT
In plain English — editorial summary, not part of the RFC
This document discusses some of the architectural implications and guidelines for implementations of Network Address Translation (NAT). This memo provides information for the Internet community.
Document record
- Document ID
- RFC2993
- Published
- November 2000
- Authors
- T. Hain
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 29
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3027Protocol Complications with the IP Network Address TranslatorCurrent
January 2001
- RFC 2185Routing Aspects of IPv6 TransitionCurrent
September 1997
- RFC 1971IPv6 Stateless Address AutoconfigurationObsoleted
August 1996
- RFC 1797Class A Subnet ExperimentCurrent
April 1995
- RFC 6052IPv6 Addressing of IPv4/IPv6 TranslatorsCurrent
October 2010
- RFC 2979Behavior of and Requirements for Internet FirewallsCurrent
October 2000
- RFC 2995Pre-Spirits Implementations of PSTN-initiated ServicesCurrent
November 2000
- RFC 2980Common NNTP ExtensionsUpdated
October 2000
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?