Last Call: <draft-ietf-opsawg-lsn-deployment-04.txt> (CGN Deployment with BGP/MPLS IP VPNs) to Informational RFC

The IESG <> Mon, 23 December 2013 16:21 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id CE36A1AE11C; Mon, 23 Dec 2013 08:21:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id iyRXTaAmq9_V; Mon, 23 Dec 2013 08:21:15 -0800 (PST)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 19A291ADF7D; Mon, 23 Dec 2013 08:21:15 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-ietf-opsawg-lsn-deployment-04.txt> (CGN Deployment with BGP/MPLS IP VPNs) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Mon, 23 Dec 2013 08:21:14 -0800
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 23 Dec 2013 16:21:17 -0000

The IESG has received a request from the Operations and Management Area
Working Group WG (opsawg) to consider the following document:
- 'CGN Deployment with BGP/MPLS IP VPNs'
  <draft-ietf-opsawg-lsn-deployment-04.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the mailing lists by 2014-01-06. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   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).  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 which 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 CGNs
   impact on the network.  This document does not intend to defend the
   merits of CGN.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.