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

Nick Hilliard <nick@foobar.org> Thu, 10 December 2020 20:53 UTC

Return-Path: <nick@foobar.org>
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 9B73D3A11DD for <ipv6@ietfa.amsl.com>; Thu, 10 Dec 2020 12:53:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 FXBLurlkj7cP for <ipv6@ietfa.amsl.com>; Thu, 10 Dec 2020 12:53:45 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [46.182.8.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A49F3A118F for <ipv6@ietf.org>; Thu, 10 Dec 2020 12:53:44 -0800 (PST)
X-Envelope-To: ipv6@ietf.org
Received: from crumpet.local (admin.ibn.ie [46.182.8.8]) (authenticated bits=0) by mail.netability.ie (8.16.1/8.16.1) with ESMTPSA id 0BAKratX091043 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Dec 2020 20:53:36 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host admin.ibn.ie [46.182.8.8] claimed to be crumpet.local
Subject: Re: For whom is IPv6? [was: Happy St Nicholas Day: Re-Launching the IPv6 ULA registry]
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: David Farmer <farmer@umn.edu>, Nico Schottelius <nico.schottelius@ungleich.ch>, IPv6 List <ipv6@ietf.org>
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>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <9ac8044e-fb3e-9417-c293-3051571e48f4@foobar.org>
Date: Thu, 10 Dec 2020 20:53:34 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.40
MIME-Version: 1.0
In-Reply-To: <b63e0c58-8e70-9c83-3f6e-6a503c20d974@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/dl7WIH_wugsQfgKPGdBi59JP3kM>
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:53:48 -0000

Brian E Carpenter wrote on 10/12/2020 19:04:
> 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?

provider independent addressing has been discussed to death at RIPE over 
the years, but most of the discussion has centered around publicly 
routeable address blocks: ULA has come up from time to time, but no-one 
ever really felt there was a need for a separate registry for it.

Unique addressing is only of interest in situations where you're 
interconnecting networks together.

What makes registered addresses relevant is the combination of 
interconnection + address permanence.  If you have no need for 
interconnection, then you can use private addressing or ULAs.  If you 
don't need permanence, then you can use your service provider's 
addresses.  It's only if you need both that public registration becomes 
an issue.

If you want registered addresses, they're cheap and readily available: a 
LIR is charged €50/y per block, where there's a demonstrated need for 
the holder to multihome (the LIR will usually mark this charge up).  So 
if there's already an option to register GUAs, what added advantage is 
there to maintain a ULA registry?  It would be less functional for no 
less cost or effort.

Nick