Re: the race to the bottom problem

Alexandre Petrescu <alexandre.petrescu@gmail.com> Sun, 08 November 2020 20:37 UTC

Return-Path: <alexandre.petrescu@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 EFF273A0CC1 for <ipv6@ietfa.amsl.com>; Sun, 8 Nov 2020 12:37:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.67
X-Spam-Level:
X-Spam-Status: No, score=0.67 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 8GqfH_fwrild for <ipv6@ietfa.amsl.com>; Sun, 8 Nov 2020 12:37:52 -0800 (PST)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D6C13A0CB7 for <ipv6@ietf.org>; Sun, 8 Nov 2020 12:37:52 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 0A8KboAA045499 for <ipv6@ietf.org>; Sun, 8 Nov 2020 21:37:50 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 6D3EF200F23 for <ipv6@ietf.org>; Sun, 8 Nov 2020 21:37:50 +0100 (CET)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 47F7D202771 for <ipv6@ietf.org>; Sun, 8 Nov 2020 21:37:50 +0100 (CET)
Received: from [10.11.240.104] ([10.11.240.104]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 0A8KbnNC006289 for <ipv6@ietf.org>; Sun, 8 Nov 2020 21:37:50 +0100
Subject: Re: the race to the bottom problem
To: ipv6@ietf.org
References: <60a15726-ff04-a202-4df9-79a6c6f33540@foobar.org> <99B762B0-0370-4B5B-9075-F688284D614A@fugue.com> <190c5cf3-9034-4e38-235c-620ecd916750@foobar.org> <CAKD1Yr0xnWqFT8PSLxQfF8VnSqX72QEcUv7jt9KHdmZ2Mj=D5Q@mail.gmail.com> <6da066c0-8e58-9bca-fb74-f2204731295a@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <f03b43e9-b4fd-f793-0200-f04867c14612@gmail.com>
Date: Sun, 08 Nov 2020 21:37:49 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.1
MIME-Version: 1.0
In-Reply-To: <6da066c0-8e58-9bca-fb74-f2204731295a@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/5i8KTOknjB_tmMtJp_7iPHNhFwk>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 08 Nov 2020 20:37:54 -0000


Le 08/11/2020 à 02:56, Brian E Carpenter a écrit :
> On 08-Nov-20 14:35, Lorenzo Colitti wrote:
>> On Sun, 8 Nov 2020, 08:24 Nick Hilliard, <nick@foobar.org
>> <mailto:nick@foobar.org>> wrote:
>> 
>> this is the problem: I did read it, just like I've read through all
>> the other threads on this topic over the last several years. There
>> was a repeat of the usual speculation, generalisation and
>> echo-chamber mechanics which have characterised this discussion at
>> the ietf since more-or-less forever.
>> 
>> You said: "we’ve already seen clear pressure to race to the
>> bottom".
>> 
>> So I politely ask you again: please provide citations to data.
>> Then we can have a discussion.
>> 
>> 
>> Ok, I'll bite. Once. :-)
>> 
>> Here's some data:
>> 
>> https://www.ietf.org/proceedings/96/slides/slides-96-v6ops-4.pdf
>> 
>> says that 29% of survey responses says the LAN prefix size is /64.
>> This is despite pretty much every IETF and RIR document saying that
>> ISPs should assign more.
> 
> There's some 2010-vintage data at
> https://tools.ietf.org/html/rfc6036#section-2.5 suggesting that even
> then, there was a variety of practice including some /64-only
> operators. And: "Mobile operators offer /64 in accordance with 3GPP,
> but at least one would like to be allowed to offer /128 or /126."

I think that could be a good supposition to imagine that that (human) at 
operator might race to a bottom.

But there could be other reasons than racing to a bottom.

Initial IPv6 deployments at mobile operators where with ppp protocol, 
which needed only two addresses on a link, hence just a /127, or so. 
Then SLAAC on 3GPP links arrived, proposing that /64.  But some 
operators wished to _continue_ to use their /127 and not migrate up to 
/64, for backwards compatibility.

In the end, after some changes in the network, _some_ operators migrated 
all their connections to /64 and got rid of /127.  There are still some 
places that are compatible with /127 ppp IPv6 mobile connections, which 
is good, because it is simpler.

But moving uupper from /64 to /56, for example, does not happen.

Because, there is so SLAAC with a /56 either.  It is one reason.

And because there is no DHCPv6-PD on 3GPP modems either.  It is another 
reason.

Alex

> 
> Brian
> 
> -------------------------------------------------------------------- 
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6 
> --------------------------------------------------------------------
>