Re: Extending a /64

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Mon, 16 November 2020 11:36 UTC

Return-Path: <prvs=158903f461=jordi.palet@consulintel.es>
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 532DD3A0AE5 for <ipv6@ietfa.amsl.com>; Mon, 16 Nov 2020 03:36:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 zldjCVIHHbh3 for <ipv6@ietfa.amsl.com>; Mon, 16 Nov 2020 03:36:53 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) by ietfa.amsl.com (Postfix) with ESMTP id 652873A0AC3 for <ipv6@ietf.org>; Mon, 16 Nov 2020 03:36:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1605526610; x=1606131410; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type:Content-transfer-encoding; bh=wZAx+vrD xqrI+PYsh5Tvbc+hF/LpJC6M+2+Cy6iyTgM=; b=e3iZtb3nYm5s9ROkPyQG7Ib4 CdSodssDJpPfxcLLJ/1ZXHqJznv0EbKgQmcWfWzAO0W4SNoWHmN3Vmec0u08BGPh qpMLR2zHhIMrJWujKO89M/7e/VJJbQWfMF3oAvYOVGxC7reyjamdZpBvgASfkgne rfuhiIi3eSpQs0mXhGE=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Mon, 16 Nov 2020 12:36:50 +0100
X-Spam-Processed: mail.consulintel.es, Mon, 16 Nov 2020 12:36:50 +0100
Received: from [10.10.10.144] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000465203.msg for <ipv6@ietf.org>; Mon, 16 Nov 2020 12:36:49 +0100
X-MDRemoteIP: 2001:470:1f09:495:110f:4ae8:3d37:d278
X-MDHelo: [10.10.10.144]
X-MDArrival-Date: Mon, 16 Nov 2020 12:36:49 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=158903f461=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ipv6@ietf.org
User-Agent: Microsoft-MacOutlook/16.43.20110804
Date: Mon, 16 Nov 2020 12:36:48 +0100
Subject: Re: Extending a /64
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: ipv6@ietf.org
Message-ID: <882BDF6F-8152-4597-B364-26B659DEE0D8@consulintel.es>
Thread-Topic: Extending a /64
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>
In-Reply-To: <f06db586-15ed-6dd3-d09f-06a4e3759275@mccallumwhyman.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/xare_-l5ehYly5JHHZF60noEyKs>
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 11:36:54 -0000

    IMHO, RIR policies are often far too focussed on the public internet and 
    forget about non-public internets and the value of common addressing 
    plans between public and non-public internets.

[Jordi] This is incorrect. All the RIR policies are, on purpose, "ignorant" if you use the resources in the public Internet or non-public internets. If you justify that you have a need for a non-public /16, you get it.

    3. Mobile Network Prefixes (MNPs) are non-topological addresses.

[Jordi] Similarly, RIR policies don't ask you to have an addressing plan tied to topology, geography or anything similar. You can justify your needs depending on your own case. Same for many other of your points.

    7. We are boxed in

    An ATN/IPS MNP needs to be statically allocated and to be formed from 
    some initial prefix, a 39 bit aircraft identifier and some more bits for 
    subnetting. This scheme also needs to be expandable to include other 
    airspace users such as drones. If you assume 
    draft-mishra-6man-variable-slaac then you could make do with an ICAO 
    prefix that is a /20, but a /16 avoids making that assumption.

[Jordi] I understand that this is technical issue and because we have sufficient space, it should be possible to justify it to the relevant RIR and get a /16, or a /11 or whatever you need. There is no issue at all.

    8. For legal reasons, the allocation of a /16 has to be made at the IANA 
    level.

[Jordi] I don't understand the legal reasons for that. What court will tell you that it is right? IETF is responsible of the standards, and has given the mandate to IANA for allocating the space to the RIRs. IANA can't do that unless the IETF allows that, and/or there is a global policy that allows that.

   However, I
   suspect that would make it legally impossible for IANA to unilaterally
   revoke the /16 allocation. 

[Jordi] What court will have power on that?

    My guess is that the RIRs do not have the 
    authority to give away a chunk of the address space in this way and that 
    this has to be done at the IANA level.

[Jordi] This is incorrect, I've explained it already in previous emails, maybe you didn't saw them. Any of the RIRs can easily allocate the space never mind it is a /16 or a /11. You just need to justify the need. Have you tried it?

[Jordi] It is true that some RIRs, such LACNIC and AFRINIC, require that the space is used in their region (LACNIC ask for more than 50%), however, others not, and any international/multinational organization may request an allocation for example in RIPE NCC. Again, have you tried that? If you need help, I can put you in touch with the relevant people.





**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.