Re: [**EXTERNAL**] Address length needs

Alexandre Petrescu <alexandre.petrescu@gmail.com> Sun, 08 November 2020 21:04 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 503BB3A0E30 for <ipv6@ietfa.amsl.com>; Sun, 8 Nov 2020 13:04:22 -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_H3=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 FSIvXfIX36cQ for <ipv6@ietfa.amsl.com>; Sun, 8 Nov 2020 13:04:20 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 9DEF13A0E3C for <ipv6@ietf.org>; Sun, 8 Nov 2020 13:04:20 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 0A8L4Ig6022571 for <ipv6@ietf.org>; Sun, 8 Nov 2020 22:04:18 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 696BA203DE6 for <ipv6@ietf.org>; Sun, 8 Nov 2020 22:04:18 +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 5EF25200CD2 for <ipv6@ietf.org>; Sun, 8 Nov 2020 22:04:18 +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 0A8L4H0J011937 for <ipv6@ietf.org>; Sun, 8 Nov 2020 22:04:17 +0100
Subject: Re: [**EXTERNAL**] Address length needs
To: ipv6@ietf.org
References: <160409741426.1448.16934303750885888002@ietfa.amsl.com> <CABNhwV1zoZpZNjb54rEys4+49H3vpebZW2g9JbO1_58eR+WnQg@mail.gmail.com> <CABNhwV3L7kz=cWu8s3X=djVf4MCwewzbEgx09TWaKzCULCjYUQ@mail.gmail.com> <9A9CE8E7-3552-4FD8-A50E-1BDCA2CB813F@employees.org> <CABNhwV0LxM7EuKo2wNtVacjewsVqdhrmSiVBmB_EL-mqJYdU3A@mail.gmail.com> <CD9F9F09-2CBC-4A72-99C0-4A9A470357ED@employees.org> <9e787ed0-a221-e413-e030-ac2553dffc8e@gmail.com> <a21c9447-730b-e2c0-81f6-46deda57f507@gmail.com> <f4635fa9-45ca-f7ec-40a2-41764e1ca74f@si6networks.com> <905bcc26-a223-53d0-6675-c35579b9a8be@gmail.com> <AAE75F7F-F8DF-4B7F-9C50-3D6C91544997@ciena.com> <2b59b2de-3597-8d35-374d-75e9b10d4d83@gmail.com> <21BC970D-8708-4090-A984-02E6E1305B94@gmail.com> <25099A60-8685-4226-8328-AA87376B62D2@ciena.com> <SN6PR02MB4512023A8418FA3BFA79F412C3EB0@SN6PR02MB4512.namprd02.prod.outlook.com> <b3d5b9e9-9b67-9371-e906-ee38ab054c0d@foobar.org> <e76cc16e-7a86-ca0c-66ea-22b0a0b81696@joelhalpern.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <77113340-c2b7-b589-b45d-d8873eeb7004@gmail.com>
Date: Sun, 08 Nov 2020 22:04:17 +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: <e76cc16e-7a86-ca0c-66ea-22b0a0b81696@joelhalpern.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/Ty-BDjusxDw9Gpx0y1bZEmSNiDo>
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 21:04:22 -0000


Le 08/11/2020 à 18:12, Joel M. Halpern a écrit :
> Fair enough.  Let's not use the phrase "race to the bottom"

[...]

> The premise in this discussion is that such an allocation would need 
> to be longer than /64.

No.

The premise would be that mobile operator continues to assign a /64 to a
smartphone but this smartphone would make a /65 out of it to put it on
its WiFi interface towards others in that hotspot.  These others would
use IIDs of length 63.

> I do not understand why.  If we are going to etend RA to support this
> (a request that seems reasonable) then why not do the extension in a
> way that respects the /64.

We have a solution proposal in which we try to extend RA to accommodate 
this longer-than-64 prefix on linux.  But it's certainly not the only 
way possible.

OpenBSD does it differently.  I think they dont add any new bit in RA 
and still implement that feature.  The problem I have with it is that 
few if any at all computers in cars are based on OpenBSD.

> It would seem to be sensible to look at solutions that do not
> violate MUSTs in existing specs before assuming solutions that change
> the MUST are necessary.

I certainly agree.

I think there are many ways out of that, including the status decisions.

Alex

> 
> Yours, Joel
> 
> PS: The airplane case is sufficiently different that I find it hard 
> to include it in the discussion.  In part because there is a LOT of 
> design that we are not free to alter in order to ask "is that the 
> right answer".  It is absolutely fair and necessary for folks to do 
> designs for their own problem space.  But those designs should 
> respect the limits that have been in place for more than 20 years. Or
> be prepared to have actual discussions of design choices.  (Tony and
> Fred mean ve3ry well, and they are doing a good job of describing the
> constraints ICAO has accepted.  But they can't change those 
> constraints or make commit to make changes.  Heck, it is not clear 
> they even agree with each other.)
> 
> On 11/8/2020 11:56 AM, Nick Hilliard wrote:
>> STARK, BARBARA H wrote on 08/11/2020 15:07:
>>> I agree. The "race to the bottom" argument is a 100% FUD 
>>> argument.
>> 
>> It's more than just FUD. The term "race to the bottom" is a 
>> politically charged phrase which is being used to shut down and 
>> obscure legitimate discussion about the complex issue of subnet 
>> size management on production networks.  Loaded language of this 
>> form has no place in an SDO working group.
>> 
>> Nick
>> 
>> --------------------------------------------------------------------
>>
>>
>> 
IETF IPv6 working group mailing list
>> ipv6@ietf.org Administrative Requests: 
>> https://www.ietf.org/mailman/listinfo/ipv6 
>> --------------------------------------------------------------------
>
>>
>> 
> --------------------------------------------------------------------
>  IETF IPv6 working group mailing list ipv6@ietf.org Administrative 
> Requests: https://www.ietf.org/mailman/listinfo/ipv6 
> --------------------------------------------------------------------