RFC 6619: Scalable Operation of Address Translators with Per-Interface Bindings

This document explains how to employ address translation in networks that serve a large number of individual customers without requiring a correspondingly…

Read RFC 6619 on the RFC Editor

Outgoing relationships (12 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Informative reference — RFC 1918: Address Allocation for Private Internets
Informative reference — RFC 1661: The Point-to-Point Protocol (PPP)
Informative reference — RFC 2663: IP Network Address Translator (NAT) Terminology and Considerations
Informative reference — RFC 4787: Network Address Translation (NAT) Behavioral Requirements for Unicast UDP
Informative reference — RFC 6146: Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers
Informative reference — RFC 4213: Basic Transition Mechanisms for IPv6 Hosts and Routers
Informative reference — RFC 6333: Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion
Informative reference — RFC 5382: NAT Behavioral Requirements for TCP
Informative reference — RFC 2516: A Method for Transmitting PPP Over Ethernet (PPPoE)
Informative reference — RFC 2993: Architectural Implications of NAT
Informative reference — RFC 6127: IPv4 Run-Out and IPv4-IPv6 Co-Existence Scenarios

Incoming relationships (3 related RFCs)

Informatively referenced by — RFC 6887: Port Control Protocol (PCP)
Informatively referenced by — RFC 7843: Port Control Protocol (PCP) Third-Party ID Option
Informatively referenced by — RFC 7974: An Experimental TCP Option for Host Identification