Re: Non routable IPv6 registry proposal

Nick Hilliard <nick@foobar.org> Thu, 21 January 2021 22:40 UTC

Return-Path: <nick@foobar.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 924B43A085E for <ietf@ietfa.amsl.com>; Thu, 21 Jan 2021 14:40:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.162
X-Spam-Level:
X-Spam-Status: No, score=-2.162 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.262, 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 iUGwoubBuWga for <ietf@ietfa.amsl.com>; Thu, 21 Jan 2021 14:39:58 -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 9A2A13A07C8 for <ietf@ietf.org>; Thu, 21 Jan 2021 14:39:58 -0800 (PST)
X-Envelope-To: ietf@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 10LMdl18003289 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jan 2021 22:39:47 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: Non routable IPv6 registry proposal
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
References: <CAMm+LwjNiE0P7RAVqzKMypNbh3=9BeqiWn_hGv3E=zX7-YmSXQ@mail.gmail.com> <abdac3dd-f601-1fae-8c9f-fbe393930558@foobar.org> <e9a49b69-b629-356b-c33a-4d49794c3e89@gmail.com> <CAMm+Lwh7nQRm=4fLkOKOgQA9L9TS_wh3qSmmV_Ko+N+afDtw+Q@mail.gmail.com> <7f73201d-7f28-92ff-875f-12133e278f94@foobar.org> <CAMm+Lwif4fB_kr7F=hR_nzPhESbqk55E2ZF6o51vC3tDmGCfEw@mail.gmail.com> <babb667b-fd2d-dc0c-8979-63d51ded7c05@foobar.org> <CAMm+Lwjdxa3H1zfae=mQKnuSM--jicN_qCTiBKi3Fe1oBW-P_A@mail.gmail.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <80df0475-a866-6491-7ade-f3d1e4f341f4@foobar.org>
Date: Thu, 21 Jan 2021 22:39:45 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.45
MIME-Version: 1.0
In-Reply-To: <CAMm+Lwjdxa3H1zfae=mQKnuSM--jicN_qCTiBKi3Fe1oBW-P_A@mail.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/ietf/kVzKdw6y8qoe8uIBrgtgUcrJl1I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2021 22:40:03 -0000

Phillip Hallam-Baker wrote on 21/01/2021 16:00:
> Perhaps we should ask how registries can go wrong. Or maybe we should 
> ask the IAB to consider this.I can think of a few problems:
> 
> Integrity
> * Duplicate registrations
> * Unauthorized registration modification
> * Unpublished registrations
> * Inappropriate semantic mapping
> 
> Availability
> * Rent seeking
> * Denial of service
> * Coercion by government

+ practical issues: insolvency, mismanagement, internal fraud, graft, 
liabilities therefrom, corruption, threat of legal action due to 
deregistration, threats from stakeholders / owners, etc.

> OK so there is one 'risk' that perhaps should be mentioned openly 
> because it is likely the one of most concern to people, 'what are the 
> unexpected uses of these addresses' or 'what else is PHB planning he is 
> not telling us about'.

obviously raising prices 10x after lock-in has been achieved 👀

There's no shortage of failure modes.

> The registry concern that is rarely considered in IETF is what happens 
> if there is no registry? There are two possibilities:
> 
> 1) Innovation is put on hold until the registry is created.
> 2) People just create their own code points
> 
> The second has occurred on countless occasions and sometimes between 
> really big companies. Every hard drive has a unique identifier which is 
> actually in the MAC address space. After asking nicely and getting the 
> run-around, the drive makers just allocated themselves 1/16th of the 
> total MAC address space.

does this matter to the IEEE?  I.e. is this a MAC?

Nick