Re: [Gen-art] Gen-Art review of draft-ietf-opsawg-lsn-deployment-04

Martin Thomson <martin.thomson@gmail.com> Thu, 23 January 2014 04:21 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8775C1A0157 for <gen-art@ietfa.amsl.com>; Wed, 22 Jan 2014 20:21:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-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 uInU4PwLibe2 for <gen-art@ietfa.amsl.com>; Wed, 22 Jan 2014 20:21:14 -0800 (PST)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 5E16A1A0101 for <gen-art@ietf.org>; Wed, 22 Jan 2014 20:21:14 -0800 (PST)
Received: by mail-wi0-f175.google.com with SMTP id hr1so6398827wib.8 for <gen-art@ietf.org>; Wed, 22 Jan 2014 20:21:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PvdO3oTrosumdOtPHYyVLJH5bKs9qF76FJPC2rO3CAs=; b=xROS9QTfcjYnt91hHgANvCBWzS7hAnUVchmF4Kz/xqEKSbuOpqmd5+zpuoybbL6/vE 3TlL409xqe5Y+tn0k8KhtRG6eGBuicI3GJSmwY58FYcBffV9e9I1iRW4BaWLTZufzYgC mvHuqcgg8CAYWym3Qfrpdx8MI2a4umfdmxKgYFelOASSBenx/xODLM8RB7V5XRV+0Muo 3UmglE9OK7apWgGqkYX0oRtipQHpfIm61wrgjK2ytrpGnYvD0VkDBUfXtCKtpgHaOoRi uWk6zwtB5veJJm247haCwazlE0rb9UKSAjAoYiMVxVT7LThTKFJ+B0Lkp8hpgMyxqy+W XQ6Q==
MIME-Version: 1.0
X-Received: by 10.194.79.165 with SMTP id k5mr4833707wjx.44.1390450873160; Wed, 22 Jan 2014 20:21:13 -0800 (PST)
Received: by 10.227.105.132 with HTTP; Wed, 22 Jan 2014 20:21:13 -0800 (PST)
In-Reply-To: <CAJc3aaOBz3j2F37-hjmffgpQZnPwgiEZVv_b3hFXvV4VgB9fKQ@mail.gmail.com>
References: <CABkgnnXj07R25LQ64-=bha6iFpabgAt=xsRP0+5A20wnF8JUdQ@mail.gmail.com> <CAJc3aaPKeuPicy_X+MG-T-XyZ+YdONphhkp1Ow666jq9_ubzew@mail.gmail.com> <CABkgnnWWLHKV7NZX4dZJM-YpRg4doSPKLRMD43sC9t23Pbx-VQ@mail.gmail.com> <52DFB2D9.7030300@cisco.com> <CABkgnnW6ACt95BwkFQoLPU=3d=cQ_bZAYfnuuM3OzbVahXUWww@mail.gmail.com> <CAJc3aaOBz3j2F37-hjmffgpQZnPwgiEZVv_b3hFXvV4VgB9fKQ@mail.gmail.com>
Date: Thu, 23 Jan 2014 05:21:13 +0100
Message-ID: <CABkgnnVcLjsvr69v8be4ivLohVbJSNydP+_55hm2wXp-=LXSXw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Victor Kuarsingh <victor@jvknet.com>
Content-Type: text/plain; charset="UTF-8"
Cc: Benoit Claise <bclaise@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-opsawg-lsn-deployment.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-opsawg-lsn-deployment-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 04:21:16 -0000

WFM

On 22 January 2014 23:22, Victor Kuarsingh <victor@jvknet.com> wrote:
> Martin,
>
> I am loading a new new version today, but here is that section (originally
> called "Motivation") for quick review.
>
> ** Beginning of section **
>
> Existing Network Considerations (new name of section)
>
> The selection of CGN may be made by an operator based on a number of
> factors. The overall driver to use CGN may be the depletion of IPv4 address
> pools which leaves little to no addresses for a growing IPv4 service or
> connection demand growth. IPv6 is considered the strategic answer for IPv4
> address depletion; however, the operator may independently decide that CGN
> is needed to supplement IPv6 and address their particular IPv4 service
> deployment needs.
>
> If the operator has chosen to deploy CGN, they should do this in a manner as
> not to negatively impact the existing IPv4 or IPv6 subscriber base. This
> will include solving a number of challenges since subscribers whose
> connections require translation will have network routing and flow needs
> which are different from legacy IPv4 connections.
>
> ** End of section **
>
> regards,
>
> Victor K
>
>
>
> On Wed, Jan 22, 2014 at 10:01 AM, Martin Thomson <martin.thomson@gmail.com>
> wrote:
>>
>> On 22 January 2014 13:00, Benoit Claise <bclaise@cisco.com> wrote:
>> > Is your concern that  the sentence "IPv6 is considered the strategic
>> > answer"
>> > in section 2 is not stressed enough?
>>
>>
>> I think that the text in the second paragraph is slightly more loaded.
>>  In particular,
>>
>>    These issues
>>    leave an operator in a precarious position which may lead to the
>>    decision to deploy CGN.
>>
>> The rest of the section uses similarly loaded:
>>
>>    The ability to replace IPv4-only equipment may be out of the control
>>    of the operator, and even when it's in the administrative control, it
>>    poses both cost and technical challenges as operators build out
>>    massive programs for equipment retirement or upgrade.
>>
>> "precarious position", "poses both cost and technical challenges", ...
>> all arguably true, but not strictly neutral.
>
>