Re: Extending a /64

Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> Mon, 16 November 2020 00:12 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 9D4833A07A0 for <ipv6@ietfa.amsl.com>; Sun, 15 Nov 2020 16:12:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 dm4QAmijiuWl for <ipv6@ietfa.amsl.com>; Sun, 15 Nov 2020 16:12:08 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C8FC3A0799 for <ipv6@ietf.org>; Sun, 15 Nov 2020 16:12:07 -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 m1keS7i-0000E0C; Mon, 16 Nov 2020 01:11:58 +0100
Message-Id: <m1keS7i-0000E0C@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>
In-reply-to: Your message of "Mon, 16 Nov 2020 00:01:31 +0000 ." <b022d11f-b55d-07ef-307d-949ff57cd562@foobar.org>
Date: Mon, 16 Nov 2020 01:11:58 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/E7rEKi0aW55C9p0hLpQFER3DdaY>
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 00:12:10 -0000

>If the need is shown, why would the aerospace industry not get the 
>address space?  /17 of address space for an entire industry with unified 
>networking goals doesn't seem especially unreasonable, i.e. it's very 
>large service provider size.  There aren't that many other equivalent 
>society / industry areas which have common networking goals in the same 
>way that the aerospace industry does.

Of course this is more a discussion for the relevant RIR communities, but
for example based on RIPE policies, I don't see how you could get a /17 for
around 500000 internet connections. Even if you assume a couple of 
hundred passengers per plane and a /48 per passenger then it still doesn't
add up.

In what way is the aerospace large from a network point of view? 500000
connections is not a lot. In most parts of the world that would be a smallish
ISP.