RFC 3027: Protocol Complications with the IP Network Address Translator

The purpose of this document is to identify the protocols and applications that break with NAT enroute. The document also attempts to identify any known…

Read RFC 3027 on the RFC Editor

Outgoing relationships (15 related RFCs)

Informative reference — RFC 2205: Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
Informative reference — RFC 2401: Security Architecture for the Internet Protocol
Informative reference — RFC 2406: IP Encapsulating Security Payload (ESP)
Informative reference — RFC 2402: IP Authentication Header
Informative reference — RFC 3022: Traditional IP Network Address Translator (Traditional NAT)
Informative reference — RFC 821: Simple Mail Transfer Protocol
Informative reference — RFC 2663: IP Network Address Translator (NAT) Terminology and Considerations
Informative reference — RFC 2573: SNMP Applications
Informative reference — RFC 2411: IP Security Document Roadmap
Informative reference — RFC 2543: SIP: Session Initiation Protocol
Informative reference — RFC 2993: Architectural Implications of NAT
Informative reference — RFC 2101: IPv4 Address Behaviour Today
Informative reference — RFC 2709: Security Model with Tunnel-mode IPsec for NAT Domains
Informative reference — RFC 2694: DNS extensions to Network Address Translators (DNS_ALG)
Informative reference — RFC 2962: An SNMP Application Level Gateway for Payload Address Translation

Incoming relationships (4 related RFCs)

Normatively referenced by — RFC 4966: Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status
Informatively referenced by — RFC 4787: Network Address Translation (NAT) Behavioral Requirements for Unicast UDP
Informatively referenced by — RFC 3927: Dynamic Configuration of IPv4 Link-Local Addresses
Informatively referenced by — RFC 6740: Identifier-Locator Network Protocol (ILNP) Architectural Description