RFC 7289: Carrier-Grade NAT (CGN) Deployment with BGP/MPLS IP VPNs
In plain English — editorial summary, not part of the RFC
This document specifies a framework to integrate a Network Address Translation (NAT) layer into an operator's network to function as a Carrier-Grade NAT (also known as CGN or Large-Scale NAT). The CGN infrastructure will often form a NAT444 environment as the subscriber home network will likely also maintain a subscriber-side NAT function. Exhaustion of the IPv4 address pool is a major driver compelling some operators to implement CGN. Although operators may wish to deploy IPv6 to strategically overcome IPv4 exhaustion, near- term needs may not be satisfied with an IPv6 deployment alone. This document provides a practical integration model that allows the CGN platform to be integrated into the network, meeting the connectivity needs of the subscriber while being mindful of not disrupting existing services and meeting the technical challenges that CGN brings. The model included in this document utilizes BGP/MPLS IP VPNs, which allow for virtual routing separation, helping ease the CGN's impact on the network. This document does not intend to defend the merits of CGN.
Document record
- Document ID
- RFC7289
- Published
- June 2014
- Authors
- V. Kuarsingh; J. Cianfarani
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7857Updates to Network Address Translation (NAT) Behavioral RequirementsCurrent
April 2016
- RFC 6127IPv4 Run-Out and IPv4-IPv6 Co-Existence ScenariosCurrent
May 2011
- RFC 7290Test Plan and Results for Advancing RFC 2680 on the Standards TrackCurrent
July 2014
- RFC 7286Application-Layer Traffic Optimization (ALTO) Server DiscoveryCurrent
November 2014
- RFC 7285Application-Layer Traffic Optimization (ALTO) ProtocolUpdated
September 2014
- RFC 7278Extending an IPv6 /64 Prefix from a Third Generation Partnership Project (3GPP) Mobile Interface to a LAN LinkCurrent
June 2014
- RFC 7277A YANG Data Model for IP ManagementObsoleted
June 2014
- RFC 7276An Overview of Operations, Administration, and Maintenance (OAM) ToolsCurrent
June 2014
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?