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

"Joel M. Halpern" <jmh@joelhalpern.com> Sun, 08 November 2020 17:12 UTC

Return-Path: <jmh@joelhalpern.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 9B91B3A0D9B for <ipv6@ietfa.amsl.com>; Sun, 8 Nov 2020 09:12:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 uk2eGQBSnpyM for <ipv6@ietfa.amsl.com>; Sun, 8 Nov 2020 09:12:39 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 F2C813A0D90 for <ipv6@ietf.org>; Sun, 8 Nov 2020 09:12:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4CTgft58BGz1ntWq; Sun, 8 Nov 2020 09:12:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1604855558; bh=cNTpv6IIAgRtBfnl77V0XcSLcFhEu2LB3CkwxzllRYM=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=Pls6gVYmBPsU858lk7KsE2+kRm7NuVIT81Zf3iZub901oMbgLLo1cgsb3xZdNC2zc vsmT74TUs3vNpQb5Kl8OmRxti2JZd9Ta9v89h7uYmxxH470oTS7+/F/pXrOzuPuHRB kMlucyyOnNEtJddvEgdhTXqpdkbpCDGx/OOqBuhc=
X-Quarantine-ID: <fj_iapY38ppW>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.128.43] (unknown [50.225.209.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4CTgfs1jH7z1ntTS; Sun, 8 Nov 2020 09:12:37 -0800 (PST)
Subject: Re: [**EXTERNAL**] Address length needs
To: Nick Hilliard <nick@foobar.org>, "STARK, BARBARA H" <bs7652@att.com>
Cc: 'IPv6 List' <ipv6@ietf.org>
References: <160409741426.1448.16934303750885888002@ietfa.amsl.com> <3c1c3ab5-5726-b141-e7ed-618984bbbdb1@gmail.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>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <e76cc16e-7a86-ca0c-66ea-22b0a0b81696@joelhalpern.com>
Date: Sun, 08 Nov 2020 12:12:36 -0500
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: <b3d5b9e9-9b67-9371-e906-ee38ab054c0d@foobar.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/TBIF5bzuq85V7Cz5Lf1CucPw5LI>
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 17:12:41 -0000

Fair enough.  Let's not use the phrase "race to the bottom"

We can observe that some operators have indicated in reputable surveys 
that they would like to allocate /126 to customers.

We know, from both experience and analysis, that any particular number 
is hard to defend.  We could say the longest assignment to a UE / Node / 
... had to be /96.  And we would get arguments about why it needed to be 
longer.  We agreed during the design of IPv6, on the /64 in part so that 
we would not have to repeat the argument eveyr time we turned around.

there is a fair question about how an operator who is not using DHCPv6 
for address assignment (whether mobile or fixed) can use RA to give out 
a prefix to a piece of equipment that can be used for suballocation. 
The premise in this discussion is that such an allocation would need to 
be longer than /64.  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.

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.

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
> --------------------------------------------------------------------