RFC 6888: Common Requirements for Carrier-Grade NATs (CGNs)
In plain English — editorial summary, not part of the RFC
This document defines common requirements for Carrier-Grade NATs (CGNs). It updates RFC 4787.
Document record
- Document ID
- RFC6888
- Published
- April 2013
- Authors
- S. Perreault; I. Yamagata; S. Miyakawa; A. Nakagawa; H. Ashida
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- tsv
- Pages
- 15
- Also known as
- BCP127
- Updates:
- RFC 4787
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6598IANA-Reserved IPv4 Prefix for Shared Address SpaceCurrent
April 2012
- RFC 7648Port Control Protocol (PCP) Proxy FunctionCurrent
September 2015
- RFC 8045RADIUS Extensions for IP Port Configuration and ReportingCurrent
January 2017
- RFC 6773DCCP-UDP: A Datagram Congestion Control Protocol UDP Encapsulation for NAT TraversalCurrent
November 2012
- RFC 7021Assessing the Impact of Carrier-Grade NAT on Network ApplicationsCurrent
September 2013
- RFC 6535Dual-Stack Hosts Using "Bump-in-the-Host" (BIH)Current
February 2012
- RFC 6062Traversal Using Relays around NAT (TURN) Extensions for TCP AllocationsCurrent
November 2010
- RFC 6052IPv6 Addressing of IPv4/IPv6 TranslatorsCurrent
October 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?