[OPSAWG] Last Call: <draft-ietf-opsawg-lsn-deployment-04.txt> (CGN Deployment with BGP/MPLS IP VPNs) to Informational RFC
The IESG <iesg-secretary@ietf.org> Mon, 23 December 2013 16:21 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE36A1AE11C; Mon, 23 Dec 2013 08:21:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iyRXTaAmq9_V; Mon, 23 Dec 2013 08:21:15 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (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 <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <20131223162114.32344.30187.idtracker@ietfa.amsl.com>
Date: Mon, 23 Dec 2013 08:21:14 -0800
Cc: opsawg@ietf.org
Subject: [OPSAWG] Last Call: <draft-ietf-opsawg-lsn-deployment-04.txt> (CGN Deployment with BGP/MPLS IP VPNs) to Informational RFC
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=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 ietf@ietf.org mailing lists by 2014-01-06. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract 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 http://datatracker.ietf.org/doc/draft-ietf-opsawg-lsn-deployment/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-opsawg-lsn-deployment/ballot/ No IPR declarations have been submitted directly on this I-D.