Re: Extending a /64

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 10 November 2020 01:56 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 D617D3A1589 for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 17:56:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 JeUFLJBwS_7i for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 17:56:04 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87D543A1586 for <ipv6@ietf.org>; Mon, 9 Nov 2020 17:56:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 8528038A68; Mon, 9 Nov 2020 20:56:26 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 9i0JrJA_1mDS; Mon, 9 Nov 2020 20:56:26 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 0664438A13; Mon, 9 Nov 2020 20:56:26 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 38E0C558; Mon, 9 Nov 2020 20:56:02 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>, ipv6@ietf.org
Subject: Re: Extending a /64
In-Reply-To: <5B4CE94D-F7B9-4211-8E1D-6715AF78340C@consulintel.es>
References: <005ECBB3-088B-4363-BB53-8D4AD25CA3D2@employees.org> <b468124f-f85b-7e20-a354-c6b7eaba3447@mccallumwhyman.com> <5B4CE94D-F7B9-4211-8E1D-6715AF78340C@consulintel.es>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Mon, 09 Nov 2020 20:56:02 -0500
Message-ID: <23374.1604973362@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/JK8eqoKNZNVN4gb_65DohKd4cb0>
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: Tue, 10 Nov 2020 01:56:06 -0000

JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org> wrote:
    > IANA can't directly allocate to ISPs or end-users, unless the IETF
    > documents a special case, which I don't think is required because it
    > can perfectly follow the existing policies in the relevant RIR.

I believe that this is exactly what Tony is here to do.

    > You need to follow the process with the relevant RIR, according to
    > their existing policies. I understand that in the case of ICAO, it will
    > be ARIN.

I don't believe that ARIN (or any of the RIRs) is allowed to allocate address
space that won't be used in it's region.
So while it might be reasonable for an *airport* to go to it's local RIR, the
rest of the infrastructure moves all over the place.

ICAO essentially needs to be a RIR of sorts.

    > Even allocating a /48 to each possible human in the earth, there is not
    > any problem. See slide 6 at:

Sure.  I don't know if ICAO needs a /16 (vs a /18 or /22).
This is something we should debate on the basis of engineering trade offs.
If we won't give people the address space they need, then they will push the
/64 boundary.

(And Ole, sorry to continue off of your intended thread. But, your question
is too big)


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide