RFC 6269: Issues with IP Address Sharing

The completion of IPv4 address allocations from IANA and the Regional Internet Registries (RIRs) is causing service providers around the world to question how…

Read RFC 6269 on the RFC Editor

Outgoing relationships (22 related RFCs)

Informative reference — RFC 1918: Address Allocation for Private Internets
Informative reference — RFC 1191: Path MTU discovery
Informative reference — RFC 2782: A DNS RR for specifying the location of services (DNS SRV)
Informative reference — RFC 1700: Assigned Numbers
Informative reference — RFC 2827: Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing
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 3056: Connection of IPv6 Domains via IPv4 Clouds
Informative reference — RFC 5996: Internet Key Exchange Protocol Version 2 (IKEv2)
Informative reference — RFC 4380: Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)
Informative reference — RFC 6056: Recommendations for Transport-Protocol Port Randomization
Informative reference — RFC 6145: IP/ICMP Translation Algorithm
Informative reference — RFC 3232: Assigned Numbers: RFC 1700 is Replaced by an On-line Database
Informative reference — RFC 5961: Improving TCP's Robustness to Blind In-Window Attacks
Informative reference — RFC 3715: IPsec-Network Address Translation (NAT) Compatibility Requirements
Informative reference — RFC 2993: Architectural Implications of NAT
Informative reference — RFC 3947: Negotiation of NAT-Traversal in the IKE
Informative reference — RFC 5508: NAT Behavioral Requirements for ICMP
Informative reference — RFC 2140: TCP Control Block Interdependence
Informative reference — RFC 1337: TIME-WAIT Assassination Hazards in TCP
Informative reference — RFC 5135: IP Multicast Requirements for a Network Address Translator (NAT) and a Network Address Port Translator (NAPT)

Incoming relationships (28 related RFCs)

Normatively referenced by — RFC 6888: Common Requirements for Carrier-Grade NATs (CGNs)
Normatively referenced by — RFC 7422: Deterministic Address Mapping to Reduce Logging in Carrier-Grade NAT Deployments
Normatively referenced by — RFC 9313: Pros and Cons of IPv6 Transition Technologies for IPv4-as-a-Service (IPv4aaS)
Informatively referenced by — RFC 6973: Privacy Considerations for Internet Protocols
Informatively referenced by — RFC 6598: IANA-Reserved IPv4 Prefix for Shared Address Space
Informatively referenced by — RFC 6555: Happy Eyeballs: Success with Dual-Stack Hosts
Informatively referenced by — RFC 7597: Mapping of Address and Port with Encapsulation (MAP-E)
Informatively referenced by — RFC 6343: Advisory Guidelines for 6to4 Deployment
Informatively referenced by — RFC 7626: DNS Privacy Considerations
Informatively referenced by — RFC 7596: Lightweight 4over6: An Extension to the Dual-Stack Lite Architecture
Informatively referenced by — RFC 6302: Logging Recommendations for Internet-Facing Servers
Informatively referenced by — RFC 7239: Forwarded HTTP Extension
Informatively referenced by — RFC 6540: IPv6 Support Required for All IP-Capable Nodes
Informatively referenced by — RFC 7599: Mapping of Address and Port using Translation (MAP-T)
Informatively referenced by — RFC 9099: Operational Security Considerations for IPv6 Networks
Informatively referenced by — RFC 8404: Effects of Pervasive Encryption on Operators
Informatively referenced by — RFC 6967: Analysis of Potential Solutions for Revealing a Host Identifier (HOST_ID) in Shared Address Deployments
Informatively referenced by — RFC 7225: Discovering NAT64 IPv6 Prefixes Using the Port Control Protocol (PCP)
Informatively referenced by — RFC 8170: Planning for Protocol Adoption and Subsequent Transitions
Informatively referenced by — RFC 8803: 0-RTT TCP Convert Protocol
Informatively referenced by — RFC 7857: Updates to Network Address Translation (NAT) Behavioral Requirements
Informatively referenced by — RFC 9632: Finding and Using Geofeed Data
Informatively referenced by — RFC 6908: Deployment Considerations for Dual-Stack Lite
Informatively referenced by — RFC 7393: Using the Port Control Protocol (PCP) to Update Dynamic DNS
Informatively referenced by — RFC 7618: Dynamic Allocation of Shared IPv4 Addresses
Informatively referenced by — RFC 7620: Scenarios with Host Identification Complications
Informatively referenced by — RFC 6782: Wireline Incremental IPv6
Informatively referenced by — RFC 7974: An Experimental TCP Option for Host Identification