Re: [OPSAWG] Request for feedback: draft-weil-opsawg-provider-address-space-02

Arturo Servin <arturo.servin@gmail.com> Fri, 29 October 2010 15:43 UTC

Return-Path: <arturo.servin@gmail.com>
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3246F3A6A51 for <opsawg@core3.amsl.com>; Fri, 29 Oct 2010 08:43:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 54ywu0fQiMQv for <opsawg@core3.amsl.com>; Fri, 29 Oct 2010 08:43:04 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id B5F243A69CB for <opsawg@ietf.org>; Fri, 29 Oct 2010 08:43:04 -0700 (PDT)
Received: by gxk7 with SMTP id 7so2215877gxk.31 for <opsawg@ietf.org>; Fri, 29 Oct 2010 08:44:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=hrflfY1hsGf7DH1Q6k94VRT2qixT3+i5CQAByE08R+M=; b=c3cK1s0PxSujXw3DlqaX5EkLE9JBaweQ+O+QP68BCo78ISHM+9ohK1jT+mcKQ8qA4K oDLDlNUQVQPPHoLGVYLLwFfEjkuxlwbrPJgwSLo/YxC7yzd8b5TD198FAUD2W3EWqx1p uFc34TTat9xT3VCD0E3LQqXk5iYQZHhwwgU5w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=wAVhIBN/K25LG0VGAooHnkH0wh3KzCQ0vvjfBzqm7McppRBPDuHROXV7CHh6zhJH1s 75hp9Ebmm1zya0sfj1tyfTYKhtW6l5e5mWw+qxtn+Fb4qQcM14YsFSUxfyI+Axwl0mPG xJhRPC5kK0mPsJ5NpyNwm89cGeji/EpLzUaC8=
Received: by 10.151.9.11 with SMTP id m11mr3483383ybi.71.1288367098208; Fri, 29 Oct 2010 08:44:58 -0700 (PDT)
Received: from 85-7-200.lacnic.net.uy ([200.7.85.188]) by mx.google.com with ESMTPS id s19sm6882089ybm.17.2010.10.29.08.44.55 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 29 Oct 2010 08:44:56 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Arturo Servin <arturo.servin@gmail.com>
In-Reply-To: <C8F031A7.7BEC%victor.kuarsingh@gmail.com>
Date: Fri, 29 Oct 2010 13:44:51 -0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A87264C7-1825-4F7E-B1E5-741EAA314126@gmail.com>
References: <C8F031A7.7BEC%victor.kuarsingh@gmail.com>
To: opsawg@ietf.org
X-Mailer: Apple Mail (2.1081)
Subject: Re: [OPSAWG] Request for feedback: draft-weil-opsawg-provider-address-space-02
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 29 Oct 2010 15:43:07 -0000

Victor,

On 29 Oct 2010, at 10:09, Victor Kuarsingh wrote:

> Arturo,
> 
> I do not think the draft was targeted at explicitly fixing the concerns of
> specific issues documented with using this type of address space.

	Considering the implications on the adoption of this draft as RFC I think that it should. But that is only IMHO.

> 
> Rather, it shows that this is a viable option and less impacting then other
> options.  

	I think it only shows the benefits but it does not make any comparisons. At least it is not clear for me how it has less impact than other options, may be I just missed it.

> Unfortunately, something will happen.. Operators will be forced to
> do something to expand IPv4 along side adding in IPv4.
> 
> I think the major concern is that it will either be more controlled and
> deterministic, or operators will go out (whether we like them to or not) and
> implement other options (drafts like
> draft-azinger-additional-private-ipv4-space-issues explain some of those
> other options).

	Hopefully it would be native IPv6.

> 
> We feel the case is that this is "better" then the alternatives such as
> "camping out on other IPv4 space", or many providers making a run at the
> IPv4 pool with individual requests for such space (which in the end will end
> up being the same thing but using potentially more addresses as pointed
> out).

	Not sure If I agree with you, but the case is that this argument is not clear in the text. Again, probably it is there and I just missed.

> 
> Regards,
> 
> Victor Kuarsingh

Best wishes,
als

> 
> 
> On 28/10/10 10:43 PM, "Arturo Servin" <arturo.servin@gmail.com> wrote:
> 
>> 
>> On 27 Oct 2010, at 15:54, Brian E Carpenter wrote:
>> 
>>> The arguments why this is a really bad idea have been made
>>> often enough, so I won't repeat them here. I think that
>>> the IETF should continue to not endorse the creation of yet
>>> more ambiguous unroutable address space.
>> 
>> Agree. I think the proposal has more cons than pros and those have been said
>> repeatedly. The new draft does not seem to address those concerns.
>> 
>> Regards,
>> -as
>> 
>> 
>> _______________________________________________
>> OPSAWG mailing list
>> OPSAWG@ietf.org
>> https://www.ietf.org/mailman/listinfo/opsawg
> 
> 
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg