Re: Extending a /64

Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> Sun, 15 November 2020 23:58 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 553DB3A1134 for <ipv6@ietfa.amsl.com>; Sun, 15 Nov 2020 15:58:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 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, 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 GjGUD5SsEmu7 for <ipv6@ietfa.amsl.com>; Sun, 15 Nov 2020 15:58:53 -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 43C623A1133 for <ipv6@ietf.org>; Sun, 15 Nov 2020 15:58:52 -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 m1keRv0-0000EWC; Mon, 16 Nov 2020 00:58:50 +0100
Message-Id: <m1keRv0-0000EWC@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: <005ECBB3-088B-4363-BB53-8D4AD25CA3D2@employees.org> <b468124f-f85b-7e20-a354-c6b7eaba3447@mccallumwhyman.com> <5B4CE94D-F7B9-4211-8E1D-6715AF78340C@consulintel.es> <CABNhwV1+5gOOUG=6DsBTFNrEN9rWdeMexhypuJJ0O4mWiDELQQ@mail.gmail.com> <9FF81EA8-039A-44E2-BDFC-44DBF2BFEDD8@consulintel.es> <CABNhwV06qk3s2NntFPOE+UFHZeG8QvjbmukvPDSu9GW=C9P-Aw@mail.gmail.com>
In-reply-to: Your message of "Sun, 15 Nov 2020 18:28:53 -0500 ." <CABNhwV06qk3s2NntFPOE+UFHZeG8QvjbmukvPDSu9GW=C9P-Aw@mail.gmail.com>
Date: Mon, 16 Nov 2020 00:58:49 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Jc4uaPpMsq6u2fCk8KnXpx-vYHA>
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, 15 Nov 2020 23:58:55 -0000

>Since allocations are done block wize and not linearly you have to account
>for future growth so generally over allocate for growth next 20 years.  So
>with that the much larger allocations.
>
>That still is small since most large ISPs like, we Verizon
>we want to scale to a billion as right now we have 150M and that's just
>domestic not worldwide.  Safe best for large ISPs is we want to scale to
>the number of humans on the planet so 7 Billion is a good number.  

This is subject to RIR policies. I.e., does a RIR accept expenential growth
over 20 years as a basis for an allocation request. Does an RIR want to
allocate space for 7 billion connections when an ISP now has 150 million
customers.

The five RIRs together form the NRO. In theory, they could reach out to the
IETF if address space policies don't fit in the space allocated.

Or we could look at the rate at which IANA allocates /12s to RIRs. See for
example https://www.nro.net/wp-content/uploads/NRO-Statistics-2020-Q2-FINAL.pdf
for the current state.

The current trent is that 2000::/3 is big enough that we can provide endusers
with /48s for a very long time. From an allocation point of view, there 
doesn't seem to be any reason to move the 64-bit boundary.