Re: Extending a /64

Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> Mon, 16 November 2020 16:59 UTC

Return-Path: <pch-b9D3CB0F5@u-1.phicoh.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 872EC3A12C5 for <ipv6@ietfa.amsl.com>; Mon, 16 Nov 2020 08:59:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.622
X-Spam-Level:
X-Spam-Status: No, score=-1.622 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.276, SPF_HELO_NONE=0.001, SPF_NONE=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 VG1FAT_-_YDS for <ipv6@ietfa.amsl.com>; Mon, 16 Nov 2020 08:59:10 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7DD63A12B6 for <ipv6@ietf.org>; Mon, 16 Nov 2020 08:58:47 -0800 (PST)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #157) id m1kehq1-0000J7C; Mon, 16 Nov 2020 17:58:45 +0100
Message-Id: <m1kehq1-0000J7C@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Subject: Re: Extending a /64
From: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.com
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> <0443de45-931d-fbda-20ab-2931383a3a8d@mccallumwhyman.com> <m1kegit-0000IcC@stereo.hq.phicoh.net> <5f8fee59-447d-d12f-6fa7-79c87841da69@mccallumwhyman.com>
In-reply-to: Your message of "Mon, 16 Nov 2020 16:32:55 +0000 ." <5f8fee59-447d-d12f-6fa7-79c87841da69@mccallumwhyman.com>
Date: Mon, 16 Nov 2020 17:58:45 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/pYyYvntSptXYmmLmgAbp0ypPBZQ>
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 16:59:12 -0000

In your letter dated Mon, 16 Nov 2020 16:32:55 +0000 you wrote:
>Perhaps the point that you are missing is that you have identified 
>examples where there is a central administrator managing a database. On 
>the other hand, there is no central administrator for civil aviation, it 
>is all devolved to individual states.
>
>In principle as well as technically, it would be possible to aggregate 
>all the databases - although the example of "herding cats" does come to 
>mind. But you have to ask the question: is it worth it?

I don't see why individual countries would want to maintain the mapping 
to IPv6 addresses. In theory one of the RIR communities could just
ask the RIR to do that for the entire world.

Even if it needs to be per country, just allocate a separate prefix to each
country and have a slightly bigger list of prefixes to filter in firewalls.
It is not as if firewalls would care about a couple of hundred prefixes.

>This is also not the only example of an IPv6 Address being used as an 
>identifier rather than a locator. For example, the type 4 SRH using IPv6 
>Addresses as policy identifiers.

And if you read the discussion regarding this, then there are quite a number
of operators who don't see the point of using IPv6 addresses for that purpose.