RFC 3022: Traditional IP Network Address Translator (Traditional NAT)

The NAT operation described in this document extends address translation introduced in RFC 1631 and includes a new type of network address and TCP/UDP port…

Read RFC 3022 on the RFC Editor

Outgoing relationships (8 related RFCs)

Obsoletes — RFC 1631: The IP Network Address Translator (NAT)
Informative reference — RFC 1122: Requirements for Internet Hosts - Communication Layers
Informative reference — RFC 1918: Address Allocation for Private Internets
Informative reference — RFC 1123: Requirements for Internet Hosts - Application and Support
Informative reference — RFC 1700: Assigned Numbers
Informative reference — RFC 1812: Requirements for IP Version 4 Routers
Informative reference — RFC 2663: IP Network Address Translator (NAT) Terminology and Considerations
Informative reference — RFC 2101: IPv4 Address Behaviour Today

Incoming relationships (54 related RFCs)

Showing 50 of 54 related RFCs.

Normatively referenced by — RFC 3715: IPsec-Network Address Translation (NAT) Compatibility Requirements
Normatively referenced by — RFC 8299: YANG Data Model for L3VPN Service Delivery
Normatively referenced by — RFC 6748: Optional Advanced Deployment Scenarios for the Identifier-Locator Network Protocol (ILNP)
Normatively referenced by — RFC 4008: Definitions of Managed Objects for Network Address Translators (NAT)
Normatively referenced by — RFC 6967: Analysis of Potential Solutions for Revealing a Host Identifier (HOST_ID) in Shared Address Deployments
Normatively referenced by — RFC 9693: Benchmarking Methodology for Stateful NATxy Gateways
Informatively referenced by — RFC 4787: Network Address Translation (NAT) Behavioral Requirements for Unicast UDP
Informatively referenced by — RFC 6887: Port Control Protocol (PCP)
Informatively referenced by — RFC 7665: Service Function Chaining (SFC) Architecture
Informatively referenced by — RFC 5382: NAT Behavioral Requirements for TCP
Informatively referenced by — RFC 5844: IPv4 Support for Proxy Mobile IPv6
Informatively referenced by — RFC 4389: Neighbor Discovery Proxies (ND Proxy)
Informatively referenced by — RFC 6824: TCP Extensions for Multipath Operation with Multiple Addresses
Informatively referenced by — RFC 7667: RTP Topologies
Informatively referenced by — RFC 4884: Extended ICMP to Support Multi-Part Messages
Informatively referenced by — RFC 4961: Symmetric RTP / RTP Control Protocol (RTCP)
Informatively referenced by — RFC 8684: TCP Extensions for Multipath Operation with Multiple Addresses
Informatively referenced by — RFC 9132: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
Informatively referenced by — RFC 5218: What Makes for a Successful Protocol?
Informatively referenced by — RFC 6528: Defending against Sequence Number Attacks
Informatively referenced by — RFC 6740: Identifier-Locator Network Protocol (ILNP) Architectural Description
Informatively referenced by — RFC 7022: Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)
Informatively referenced by — RFC 7873: Domain Name System (DNS) Cookies
Informatively referenced by — RFC 7596: Lightweight 4over6: An Extension to the Dual-Stack Lite Architecture
Informatively referenced by — RFC 5837: Extending ICMP for Interface and Next-Hop Identification
Informatively referenced by — RFC 6182: Architectural Guidelines for Multipath TCP Development
Informatively referenced by — RFC 6302: Logging Recommendations for Internet-Facing Servers
Informatively referenced by — RFC 4330: Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI
Informatively referenced by — RFC 5596: Datagram Congestion Control Protocol (DCCP) Simultaneous-Open Technique to Facilitate NAT/Middlebox Traversal
Informatively referenced by — RFC 7498: Problem Statement for Service Function Chaining
Informatively referenced by — RFC 3027: Protocol Complications with the IP Network Address Translator
Informatively referenced by — RFC 3104: RSIP Support for End-to-end IPsec
Informatively referenced by — RFC 3366: Advice to link designers on link Automatic Repeat reQuest (ARQ)
Informatively referenced by — RFC 5189: Middlebox Communication (MIDCOM) Protocol Semantics
Informatively referenced by — RFC 6013: TCP Cookie Transactions (TCPCT)
Informatively referenced by — RFC 6222: Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)
Informatively referenced by — RFC 6732: 6to4 Provider Managed Tunnels
Informatively referenced by — RFC 6886: NAT Port Mapping Protocol (NAT-PMP)
Informatively referenced by — RFC 8782: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
Informatively referenced by — RFC 5677: IEEE 802.21 Mobility Services Framework Design (MSFD)
Informatively referenced by — RFC 7658: Deprecation of MIB Module NAT-MIB: Managed Objects for Network Address Translators (NATs)
Informatively referenced by — RFC 7857: Updates to Network Address Translation (NAT) Behavioral Requirements
Informatively referenced by — RFC 6647: Email Greylisting: An Applicability Statement for SMTP
Informatively referenced by — RFC 6908: Deployment Considerations for Dual-Stack Lite
Informatively referenced by — RFC 7157: IPv6 Multihoming without Network Address Translation
Informatively referenced by — RFC 8151: Use Cases for Data Center Network Virtualization Overlay Networks
Informatively referenced by — RFC 8158: IP Flow Information Export (IPFIX) Information Elements for Logging NAT Events
Informatively referenced by — RFC 8280: Research into Human Rights Protocol Considerations
Informatively referenced by — RFC 6736: Diameter Network Address and Port Translation Control Application
Informatively referenced by — RFC 7584: Session Traversal Utilities for NAT (STUN) Message Handling for SIP Back-to-Back User Agents (B2BUAs)