RFC 6888: Common Requirements for Carrier-Grade NATs (CGNs)

This document defines common requirements for Carrier-Grade NATs (CGNs). It updates RFC 4787.

Read RFC 6888 on the RFC Editor

Outgoing relationships (19 related RFCs)

Updates, Normative reference — RFC 4787: Network Address Translation (NAT) Behavioral Requirements for Unicast UDP
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 793: Transmission Control Protocol
Normative reference — RFC 1122: Requirements for Internet Hosts - Communication Layers
Normative reference — RFC 2827: Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing
Normative reference — RFC 2663: IP Network Address Translator (NAT) Terminology and Considerations
Normative reference — RFC 6146: Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers
Normative reference — RFC 6887: Port Control Protocol (PCP)
Normative reference — RFC 6269: Issues with IP Address Sharing
Normative reference — RFC 6333: Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion
Normative reference — RFC 5382: NAT Behavioral Requirements for TCP
Normative reference — RFC 6056: Recommendations for Transport-Protocol Port Randomization
Normative reference — RFC 4963: IPv4 Reassembly Errors at High Data Rates
Normative reference — RFC 5508: NAT Behavioral Requirements for ICMP
Normative reference — RFC 5461: TCP's Reaction to Soft Errors
Normative reference — RFC 6264: An Incremental Carrier-Grade NAT (CGN) for IPv6 Transition
Normative reference — RFC 6302: Logging Recommendations for Internet-Facing Servers
Normative reference — RFC 5597: Network Address Translation (NAT) Behavioral Requirements for the Datagram Congestion Control Protocol
Normative reference — RFC 4008: Definitions of Managed Objects for Network Address Translators (NAT)

Incoming relationships (17 related RFCs)

Normatively referenced by — RFC 8803: 0-RTT TCP Convert Protocol
Normatively referenced by — RFC 9313: Pros and Cons of IPv6 Transition Technologies for IPv4-as-a-Service (IPv4aaS)
Normatively referenced by — RFC 8158: IP Flow Information Export (IPFIX) Information Elements for Logging NAT Events
Informatively referenced by — RFC 6887: Port Control Protocol (PCP)
Informatively referenced by — RFC 8900: IP Fragmentation Considered Fragile
Informatively referenced by — RFC 9099: Operational Security Considerations for IPv6 Networks
Informatively referenced by — RFC 6889: Analysis of Stateful 64 Translation
Informatively referenced by — RFC 8782: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
Informatively referenced by — RFC 6947: The Session Description Protocol (SDP) Alternate Connectivity (ALTC) Attribute
Informatively referenced by — RFC 7857: Updates to Network Address Translation (NAT) Behavioral Requirements
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 7289: Carrier-Grade NAT (CGN) Deployment with BGP/MPLS IP VPNs
Informatively referenced by — RFC 7584: Session Traversal Utilities for NAT (STUN) Message Handling for SIP Back-to-Back User Agents (B2BUAs)
Informatively referenced by — RFC 7974: An Experimental TCP Option for Host Identification
Informatively referenced by — RFC 10001: Operational Guidelines for DNS Transport in Mixed IPv4/IPv6 Environments