Re: For whom is IPv6? [was: Happy St Nicholas Day: Re-Launching the IPv6 ULA registry]

Michael Richardson <mcr@sandelman.ca> Thu, 10 December 2020 20:36 UTC

Return-Path: <mcr@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 A3ADF3A08F4 for <ipv6@ietfa.amsl.com>; Thu, 10 Dec 2020 12:36:41 -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=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 Nb8i4EuiaM-w for <ipv6@ietfa.amsl.com>; Thu, 10 Dec 2020 12:36:39 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F50A3A0658 for <ipv6@ietf.org>; Thu, 10 Dec 2020 12:36:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 79AD6389C5 for <ipv6@ietf.org>; Thu, 10 Dec 2020 15:38:56 -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 e_6YhLsuZiWM for <ipv6@ietf.org>; Thu, 10 Dec 2020 15:38:54 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 5075A389C0 for <ipv6@ietf.org>; Thu, 10 Dec 2020 15:38:54 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B9A91550 for <ipv6@ietf.org>; Thu, 10 Dec 2020 15:36:34 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: IPv6 List <ipv6@ietf.org>
Subject: Re: For whom is IPv6? [was: Happy St Nicholas Day: Re-Launching the IPv6 ULA registry]
In-Reply-To: <b63e0c58-8e70-9c83-3f6e-6a503c20d974@gmail.com>
References: <87r1o3deni.fsf@ungleich.ch> <CAKD1Yr3ptRjewThToEgERUOKwehTwdqNUAq14acc_nHLFqf3bg@mail.gmail.com> <87im9ds0z9.fsf@ungleich.ch> <fc637d64-a763-e5cf-fb93-002babe5f9ae@foobar.org> <87v9dcr37w.fsf@ungleich.ch> <CA+9kkMCb9fJQFJaP5ZaiwkQ2nRS7Fsn+q=C5OCPqdmMZRLSBKg@mail.gmail.com> <87sg8fp8ez.fsf@ungleich.ch> <47d1fbd9-8979-91af-240f-ec8c86f15e8d@gmail.com> <87h7ouoww4.fsf@ungleich.ch> <CAN-Dau06FTQr_c8C=cqgFGuPZ-KN2pbT-RmTHTEOkMZF0QWmNQ@mail.gmail.com> <b63e0c58-8e70-9c83-3f6e-6a503c20d974@gmail.com>
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: Thu, 10 Dec 2020 15:36:34 -0500
Message-ID: <6983.1607632594@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/H8DXi9nNkyQhK6bcWCeettjgAYU>
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: Thu, 10 Dec 2020 20:36:42 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    > I think David has it right. The confusing aspect of Nico's argument, to
    > me, is that ULAs can never be of any use for wider connectivity outside
    > the organisation that "owns" the ULA prefix, *by the very definition of
    > ULAs*.  It doesn't matter in the slightest if "Hamburg" and "Berlin"
    > use (by pure chance) the same ULA prefix, because there is no
    > connection between both of them via various ISPs, and then *by

That's not correct.  That's very much capital-Internet bias.
It's IPv4 scarcity think.  IP is for all sorts of uses that might not involve the *I*nternet.

There may be no connection via the *DFZ*.
You might never be able to reach these networks from NZ.

That doesn't mean there is no connection.
It could be a hundred 100m 802.15.4 radios running on solar power.

    > What costs money with a routeable prefix is not the prefix, it's the
    > routeability and the connectivity.
    > If that's a problem, it can only be
    > solved by some such RIR policy approach as David describes. Has RIPE
    > never considered this?

Routeability has never been promises by RIRs.
Connectivity is and has always been by 1:1 contract.

What the RIRs promise are:
  1) uniqueness.
  2) whois and reverse DNS
  3) RPSL and RPKI [added this decade]


--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [