Re: Extending a /64

Tony Whyman <tony.whyman@mccallumwhyman.com> Mon, 16 November 2020 16:33 UTC

Return-Path: <tony.whyman@mccallumwhyman.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 69DFD3A126C for <ipv6@ietfa.amsl.com>; Mon, 16 Nov 2020 08:33:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 02oSJZDExrWl for <ipv6@ietfa.amsl.com>; Mon, 16 Nov 2020 08:33:04 -0800 (PST)
Received: from mail2.mwassocs.co.uk (mail2.mwassocs.co.uk [IPv6:2a00:da00:1800:8030::1]) (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 3CAC83A128E for <ipv6@ietf.org>; Mon, 16 Nov 2020 08:33:03 -0800 (PST)
Received: from [IPv6:2a02:390:813f:1:3487:371b:4fdd:2c6d] ([IPv6:2a02:390:813f:1:3487:371b:4fdd:2c6d]) (authenticated bits=0) by mail2.mwassocs.co.uk (8.15.2/8.15.2/Debian-3) with ESMTPSA id 0AGGX1Fa003988 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 16 Nov 2020 16:33:02 GMT
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> <0443de45-931d-fbda-20ab-2931383a3a8d@mccallumwhyman.com> <m1kegit-0000IcC@stereo.hq.phicoh.net>
From: Tony Whyman <tony.whyman@mccallumwhyman.com>
Message-ID: <5f8fee59-447d-d12f-6fa7-79c87841da69@mccallumwhyman.com>
Date: Mon, 16 Nov 2020 16:32:55 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <m1kegit-0000IcC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/WBn6x7MeGYdTLFTPPD8ceNHMS6w>
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:33:05 -0000

On 16/11/2020 15:47, Philip Homburg wrote:
> I find it fascinating that telco's can associate phone numbers with IMSIs for
> billions of phones. Governments can associate license plates with VINs for
> millions of cars, but somehow the aviation industry cannot associate IPv6
> addresses with existing aircraft identifiers.

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?

In many ways, an MNP is a name and the mobility routing problem is to 
first register a care-of address for that name and then to provide a 
means of looking up the (care-of) address for a given MNP (name).

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.