Re: Extending a /64

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 16 November 2020 15:42 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 59E303A11DE for <ipv6@ietfa.amsl.com>; Mon, 16 Nov 2020 07:42:40 -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_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] 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 Fy9UMFAIQyhw for <ipv6@ietfa.amsl.com>; Mon, 16 Nov 2020 07:42:39 -0800 (PST)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 221AC3A11D8 for <ipv6@ietf.org>; Mon, 16 Nov 2020 07:42:38 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 0AGFgbBV022802; Mon, 16 Nov 2020 16:42:37 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 097942063D4; Mon, 16 Nov 2020 16:42:37 +0100 (CET)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id F02072063BA; Mon, 16 Nov 2020 16:42:36 +0100 (CET)
Received: from [10.11.240.254] ([10.11.240.254]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 0AGFgaKJ024760; Mon, 16 Nov 2020 16:42:36 +0100
Subject: Re: Extending a /64
To: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>, ipv6@ietf.org
References: <202011151920.0AFJKN9U003337@mail2.mwassocs.co.uk> <3d26bffe-b6c9-4ed7-6135-a515f9902fd7@gmail.com> <m1keOTi-0000EGC@stereo.hq.phicoh.net> <CAO42Z2wZkXryhw1u5WAFdtCvXHyyz1zeM22FP_gRxjurjsG-Jw@mail.gmail.com> <5f505585-1328-d942-2ec2-a2d96b7b4779@foobar.org> <m1kePdR-0000I6C@stereo.hq.phicoh.net> <b022d11f-b55d-07ef-307d-949ff57cd562@foobar.org> <m1keS7i-0000E0C@stereo.hq.phicoh.net> <f06db586-15ed-6dd3-d09f-06a4e3759275@mccallumwhyman.com> <m1kecJm-0000EOC@stereo.hq.phicoh.net> <5101F72E-4197-4E58-8DEF-9EB9D5541482@thehobsons.co.uk> <m1kefWI-0000ETC@stereo.hq.phicoh.net> <845e43f9-4534-a125-3105-9d345b85029f@mccallumwhyman.com> <f18f1e55-6c8f-2963-7e3a-f22a89dda46d@joelhalpern.com> <6e4114f9-c658-26b3-2fdd-5a1650342f3f@gmail.com> <m1kegEk-0000KIC@stereo.hq.phicoh.net>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <9c2491ba-593a-5cdf-269c-523887cbdb86@gmail.com>
Date: Mon, 16 Nov 2020 16:42:36 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.3
MIME-Version: 1.0
In-Reply-To: <m1kegEk-0000KIC@stereo.hq.phicoh.net>
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/tvUYe5BVK8R1NLnSGo0PtT4yPRw>
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: Mon, 16 Nov 2020 15:42:40 -0000


Le 16/11/2020 à 16:16, Philip Homburg a écrit :
>> I suspect one would not oppose embedding a 39bit airplane ID into
>> an ULA prefix, at which point the arguments about id/loc split
>> might not disallow airplane ID into GUA either.  Because routing
>> towards ULA and GUA addresses happen in the same way.
> 
> Using ULA with an airplane ID is technically a violation of RFC 4193,
> Section 3.2.1:
> "Locally assigned Global IDs MUST be generated with a pseudo-random
> "algorithm consistent with [RANDOM].

'pseudo-random'...

But I meant this text from RFC4193 ULAs:
>    This document defines a specific local method to allocate Global IDs,
>    indicated by setting the L bit to 1.  Another method, indicated by
>    clearing the L bit, may be defined later.
> [end of partial citation from RFC]


> (In theory there is also ULA-C, but that doesn't allow it either)

I dont know what is ULA-C... and why does it disallow airplane ID in a 
prefix.

Whereas I fully agree IPv6 addresses must be allocated by a central 
authority, I disagree with over specifying even the ULA contents.  I 
thought one was free to do whatever one wanted in ULA space.

Alex

>