RFC 7021: Assessing the Impact of Carrier-Grade NAT on Network Applications
In plain English — editorial summary, not part of the RFC
NAT444 is an IPv4 extension technology being considered by Service Providers as a means to continue offering IPv4 service to customers while transitioning to IPv6. This technology adds an extra Carrier- Grade NAT (CGN) in the Service Provider network, often resulting in two NATs. CableLabs, Time Warner Cable, and Rogers Communications independently tested the impacts of NAT444 on many popular Internet services using a variety of test scenarios, network topologies, and vendor equipment. This document identifies areas where adding a second layer of NAT disrupts the communication channel for common Internet applications. This document was updated to include the Dual-Stack Lite (DS-Lite) impacts also.
Document record
- Document ID
- RFC7021
- Published
- September 2013
- Authors
- C. Donley; L. Howard; V. Kuarsingh; J. Berg; J. Doshi
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 29
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6619Scalable Operation of Address Translators with Per-Interface BindingsCurrent
June 2012
- RFC 6535Dual-Stack Hosts Using "Bump-in-the-Host" (BIH)Current
February 2012
- RFC 7648Port Control Protocol (PCP) Proxy FunctionCurrent
September 2015
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
- RFC 6964Operational Guidance for IPv6 Deployment in IPv4 Sites Using the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)Current
May 2013
- RFC 7393Using the Port Control Protocol (PCP) to Update Dynamic DNSCurrent
November 2014
- RFC 5579Transmission of IPv4 Packets over Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) InterfacesCurrent
February 2010
- RFC 5569IPv6 Rapid Deployment on IPv4 Infrastructures (6rd)Current
January 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?