Re: draft-bourbaki-6man-classless-ipv6-00

Ca By <cb.list6@gmail.com> Fri, 02 June 2017 20:30 UTC

Return-Path: <cb.list6@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4ECF128B8D for <ipv6@ietfa.amsl.com>; Fri, 2 Jun 2017 13:30:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Yet6sJIXqqsx for <ipv6@ietfa.amsl.com>; Fri, 2 Jun 2017 13:30:05 -0700 (PDT)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F0091279E5 for <ipv6@ietf.org>; Fri, 2 Jun 2017 13:30:05 -0700 (PDT)
Received: by mail-yw0-x22c.google.com with SMTP id 63so24696098ywr.0 for <ipv6@ietf.org>; Fri, 02 Jun 2017 13:30:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7RytlZwO8wkxc+VaWSLjJSdVccbeAtdiRSoPFInamJc=; b=QCLc7E6fqBJncgQ4Fmd7lKE2quy8G+Ls6RXrwGmcWICzzIevqfcaOCBGwICCQitT+i voA/bv9cDX38+U/PxE9pqIK5gUd9BN8IutGNlsf3CmUu4zXcdB/ICr1wBaNb2VETPZ+F IhmpMj+PJBbcMxztxVaOJvzS4dzedDQ5YEIRLngw/awcd4FIQRC+r6VoNNVGJTnW3HOt u7fabeeCeEFpDD+6iQC5P9HK/YGRzgk+e5TGLJlk3zfJbfezMpMB0rkDIba+268M6/GY 7OzN7A9M6A6aiHbzuGle/CodB831rWOddWe1xUPFkwU8n8K2n/eoCKypsArVxzoY8bLT SMzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7RytlZwO8wkxc+VaWSLjJSdVccbeAtdiRSoPFInamJc=; b=MBYPZHPnSuPQWOLZX0lJOGoL+cwldqTakPkVh2s918s9YtL7FLV494u4L5DXfoXVn+ 7JzaGBFDaXFCpUnwe8jLNVHX25wqwwCjyPmabM7jtW8lIgkAuyS4XFLEvNGw65zomrOz Pb/C7dIvdEpVMq0MRgr+fQ6IUQ3fvAArVz83vD4TsEZXQ/x9rcBYzMzHq7RmBxSmJ++I aJGwEWcOV10l2/on9qR8BjWyFzcct8pOF+hf/XotTLt/8EMwVi6yz/X6NVFINwq8C1lH LUVZtCPHHEukwg7bs4Z/QAdXAYxPzISBwBSxoVccVOnMl0IHhnPwOGFXv5hI2Gp76OYw GdwQ==
X-Gm-Message-State: AODbwcDgod8sYWzv6Fqqh95yNNTJmGhd8+A2hXIRuF3Ys8KjLYAk+z3W wiczACGURdVWxdzexuDwPjJXqt8Kyg==
X-Received: by 10.129.62.14 with SMTP id l14mr7153884ywa.322.1496435404753; Fri, 02 Jun 2017 13:30:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.153.208 with HTTP; Fri, 2 Jun 2017 13:30:04 -0700 (PDT)
In-Reply-To: <C6696427-E3BD-4C5A-9A2F-A979CE063C45@google.com>
References: <20170602141112.x64nleqclygz7dwd@Vurt.local> <20170602141259.GD30896@gir.theapt.org> <CAKD1Yr0DtQYvCYLQexhXe_nhb5rjeyhnB4bCveqyO5Xbuwdg1A@mail.gmail.com> <20170602145655.msfjw35qhoev4sm2@Vurt.local> <CAKD1Yr3gqFgq3dxFaBEV++q5cgx1AHzFLGRJ50DYJjVE69C7iA@mail.gmail.com> <f2260ee557014429a1fef32de040547b@XCH15-06-11.nw.nos.boeing.com> <C6696427-E3BD-4C5A-9A2F-A979CE063C45@google.com>
From: Ca By <cb.list6@gmail.com>
Date: Fri, 02 Jun 2017 13:30:04 -0700
Message-ID: <CAD6AjGSTB6r8w+ioUvjivJ2hU9WENCa2opA_hAFsbP=ibU-_bQ@mail.gmail.com>
Subject: Re: draft-bourbaki-6man-classless-ipv6-00
To: james woodyatt <jhw@google.com>
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="f403045f35c2bae7e80551000479"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/fXODS_3XbcJkJ9v9pPkGGCfwScY>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jun 2017 20:30:08 -0000

On Fri, Jun 2, 2017 at 12:17 PM, james woodyatt <jhw@google.com> wrote:

> On Jun 2, 2017, at 10:14, Manfredi, Albert E <albert.e.manfredi@boeing.com>
> wrote:
>
> On Jun 2, 2017, at 09:08, Lorenzo Colitti <lorenzo@google.com> wrote:
>
>
> Example: I don't want us to have to deal with NAT any more, ever.
>
>
> I've seen this comment made before, and yet the /64 hard boundary
> practically guarantees that NAT will get used with IPv6. It's exactly the
> same solution, for exactly the same problem. Inability to expand at the
> edges.
>
>
> I have reluctantly come to believe that service providers MUST have the
> ability to force their economy class subscribers into artificially small
> allocations, so they can charge premium prices for larger ones drawn from
> the same functionally limitless supply at equivalent cost. We have to
> expect that only business and luxury class subscribers will have
> sufficiently large allocations that IPv6/NAT will add more costs than it
> saves them.
>
> I once believed IPv4/NAT was about preserving scarce number resources. I
> now think that was wrong. It was always about optimizing rents across
> differing classes of subscribers even when the extracted resource on which
> the rents are derived is practically unlimited. In this one respect, IPv6
> is no different than IPv4. As a purely technical matter, the rent MUST flow.
>
> Accordingly, I say we should stop arguing that IPv6 does not require NAT.
> For certain classes of subscriber, NAT is essential for making IPv6 service
> available at an affordable price. Indeed, any internet layer that uses
> fixed size global scope addresses requires NAT at the provider/subscriber
> boundary.
>
>
James, have you seen this situation in IPv6?  I personally have not seen
scenarios where there is class of service that requires IPv6 NAT or less
than a /64 is given.

I have also not seen in the IPv6 marketplace a scenario where cost is tied
to address space size.

Please share where this scenario is real.

Regards,
CB

>
> --james woodyatt <jhw@google.com>
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>