Re: Extending a /64

Tony Whyman <tony.whyman@mccallumwhyman.com> Sun, 08 November 2020 15:11 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 C34DA3A0C1E for <ipv6@ietfa.amsl.com>; Sun, 8 Nov 2020 07:11:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 0NqQnHLPnUd6 for <ipv6@ietfa.amsl.com>; Sun, 8 Nov 2020 07:11:33 -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 D60ED3A0B3E for <ipv6@ietf.org>; Sun, 8 Nov 2020 07:11:32 -0800 (PST)
Received: from [IPv6:2a02:390:813f:1:c4bf:8aa5:ac5c:e04a] ([IPv6:2a02:390:813f:1:c4bf:8aa5:ac5c:e04a]) (authenticated bits=0) by mail2.mwassocs.co.uk (8.15.2/8.15.2/Debian-3) with ESMTPSA id 0A8FBSoJ040397 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sun, 8 Nov 2020 15:11:29 GMT
Subject: Re: Extending a /64
To: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>, ipv6@ietf.org
References: <005ECBB3-088B-4363-BB53-8D4AD25CA3D2@employees.org> <b468124f-f85b-7e20-a354-c6b7eaba3447@mccallumwhyman.com> <m1kbksa-0000IHC@stereo.hq.phicoh.net>
From: Tony Whyman <tony.whyman@mccallumwhyman.com>
Message-ID: <78e3e2ac-8e61-84ad-cc11-ce7088304a9a@mccallumwhyman.com>
Date: Sun, 08 Nov 2020 15:11:22 +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: <m1kbksa-0000IHC@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/Ni_U0OQC8ztmVYW59WdVrKIsF_A>
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 15:11:35 -0000

On 08/11/2020 13:37, Philip Homburg wrote:
>> Our problem is that we wanted to define an addressing plan that
>> uses 39 bits to identify each aircraft,
> It seems to me that using 39 bits to number aircraft would violation
> allocation density policies. See for example Section 2.8 and Section 5.2.2
> of ripe-738 (https://www.ripe.net/publications/docs/ripe-738)
>
> (unless there are 100 billion aircraft in the world).
I would agree with that point and was why I am doubtful about whether 
the /16 application will be granted. Hence why extending beyond the /64 
boundary looks so attractive.
>
> IF the IETF directs IANA to grant this for aircraft, what happens if the
> ITU shows up and wants a prefix for phone numbers?
If they had a good enough case, why not?
>