Skip to main content

CGN Deployment with MPLS/VPNs

Document Type Replaced Internet-Draft (opsawg WG)
Expired & archived
Authors Victor Kuarsingh , John Cianfarani
Last updated 2012-07-16 (Latest revision 2012-02-20)
Replaced by draft-ietf-opsawg-lsn-deployment
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Additional resources Mailing list discussion
Stream WG state Dead WG Document
Other - see Comment Log
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-opsawg-lsn-deployment
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


This document specifies a framework to integrate a Network Address Translation layer into an operator's network to function as a Carrier Grade NAT (also known as CGN or Large Scale NAT). CGN is a concept also described in [I-D.ietf-behave-lsn-requirements] and describes the model as a dual layer translation model. 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 which allows CGN to be integrated into the network meeting the connectivity needs of the customer while being mindful of not disrupting existing services and meeting the technical challenges that CGN brings. The model includes the use of MPLS/VPNs defined in [RFC4364] as a tool to achieve this goal. This document does not intend to defend the merits of CGN.


Victor Kuarsingh
John Cianfarani

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)