Document Action: 'CGN Deployment with BGP/MPLS IP VPNs' to Informational RFC (draft-ietf-opsawg-lsn-deployment-06.txt)

The IESG <iesg-secretary@ietf.org> Mon, 14 April 2014 13:39 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 518731A0473 for <ietf-announce@ietfa.amsl.com>; Mon, 14 Apr 2014 06:39:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001] 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 Qofl_AHDRBxi; Mon, 14 Apr 2014 06:38:59 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 91F1A1A0493; Mon, 14 Apr 2014 06:38:51 -0700 (PDT)
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>
Subject: Document Action: 'CGN Deployment with BGP/MPLS IP VPNs' to Informational RFC (draft-ietf-opsawg-lsn-deployment-06.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.2.1.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140414133851.19809.49625.idtracker@ietfa.amsl.com>
Date: Mon, 14 Apr 2014 06:38:51 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/v5o5cHCTrPAdIXInO5eDwTilCy4
Cc: RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 13:39:01 -0000

The IESG has approved the following document:
- 'CGN Deployment with BGP/MPLS IP VPNs'
  (draft-ietf-opsawg-lsn-deployment-06.txt) as Informational RFC

This document is the product of the Operations and Management Area
Working Group.

The IESG contact persons are Benoit Claise and Joel Jaeggli.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-opsawg-lsn-deployment/




Technical Summary

   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.  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.

Working Group Summary

   While there was clear support for
   the document within the opsawg, there was little discussion
   and no comments during working group last call.  However, the
   authors were quite proactive about getting feedback from
   operators outside the working group context, and having
   that feedback posted to the working group mailing list, so
   we feel that the document received satisfactory expert
   review prior to and during last call.  (This was discussed
  with the OPS ADs after closing working group last call).

Document Quality

   This is a well-written document that
   clearly lays out the background, requirements, and
   deployment scenarios using straightforward, unambiguous
   language.  It received expert review from cable and telecomm
   operators during its development, and the authors are
   employed by Rogers Communication, a large Canadian telecomm
   firm. 

Personnel

   Melinda Shore is the document shepherd.
   Benoit Claise is the responsible area director