Re: Non routable IPv6 registry proposal

Phillip Hallam-Baker <phill@hallambaker.com> Thu, 21 January 2021 01:57 UTC

Return-Path: <hallam@gmail.com>
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 8CCF83A169A for <ietf@ietfa.amsl.com>; Wed, 20 Jan 2021 17:57:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level:
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 p4ezKMzBPVSv for <ietf@ietfa.amsl.com>; Wed, 20 Jan 2021 17:57:32 -0800 (PST)
Received: from mail-yb1-f181.google.com (mail-yb1-f181.google.com [209.85.219.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C98A3A1698 for <ietf@ietf.org>; Wed, 20 Jan 2021 17:57:31 -0800 (PST)
Received: by mail-yb1-f181.google.com with SMTP id f6so536753ybq.13 for <ietf@ietf.org>; Wed, 20 Jan 2021 17:57:31 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=i2+2eH/gaC6Qly0UGbczZ7TlxopgvPi2gUYXw3mZLow=; b=CIJu95Nf+MasjQ+3zYJ25NuJb59MZJhkiwgXt91w9hIVxABbiIErTTVC8ijy025EFp UttUB7QZiINDILGclPDHPbda9biJkNE5E5GjkAARVXp94OgoIuoE+0UMDMLvzz7ezBz2 CxYytAktniOKIS534cykwEh7U+JqMHsGQ23ceKakDkWkx5N4lGWLg3j/P2FkxdG7GSHr fDL8q/ZPmOfRS9kYM5fp9wn7F1alUd3GcxMncPVGVWm5YdvIdnKrLxbbpg8fDpPaySX/ OhXLnevRZRn1C3E2XxLThInkFEX5SuX4DEOLSLKBc867xyyB88hSAbFeSfm9+JtVomz4 p4yQ==
X-Gm-Message-State: AOAM530J6ZFbNt5rJvW0U8cKdC+DTdF3z5kEyP8XB7g9z3DbnbXBmUYw iXpqj/osGVJzJwcNeIAVLJaZ6JX7RnvRD4FFhgk=
X-Google-Smtp-Source: ABdhPJwAL5UdsUzyi29ossn2p7K9Wflqa8VL+KWM+/IFGyrnhbeqGz3Sz9ss5ZPoHDsu9EKCLRLCFSPdoAteEpVOJHQ=
X-Received: by 2002:a25:7704:: with SMTP id s4mr19412670ybc.523.1611194251037; Wed, 20 Jan 2021 17:57:31 -0800 (PST)
MIME-Version: 1.0
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>
In-Reply-To: <7f73201d-7f28-92ff-875f-12133e278f94@foobar.org>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 20 Jan 2021 20:57:20 -0500
Message-ID: <CAMm+Lwif4fB_kr7F=hR_nzPhESbqk55E2ZF6o51vC3tDmGCfEw@mail.gmail.com>
Subject: Re: Non routable IPv6 registry proposal
To: Nick Hilliard <nick@foobar.org>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ff4dff05b95f64a0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/W7E3gfc0yduQ7_8Q6_fuwRUIi9I>
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 01:57:34 -0000

On Wed, Jan 20, 2021 at 6:25 PM Nick Hilliard <nick@foobar.org> wrote:

> Phillip Hallam-Baker wrote on 20/01/2021 21:58:
> > So lets say I decide to start up a registry. I write up an RFC
> > describing the answers to the issues you raise and I get FC00::0000/32
> > to allocate on an experimental basis. Worst that can happen is I screw
> > up and lose track of who was allocated what. I can now issue 4 billion
> > /64s before I have to come and ask for more space.
> whoa, wait up there!  Either you have a registry or you don't.  If your
> model is ok with long term inaccuracy due to data loss, data rot, or
> cruft accumulation, then the question needs to be asked whether you
> ought to be running a registry to start with.  The whole point of a
> registry is that it provides some level of comfort about resource
> registration accuracy.
>
> Nick
>

I said worst case.

People make waaaay too much out of the risks of running registries. There
are an infinite number of petty bureaucratic objections that can be raised.
That is how PEM was killed. Oh whatabout this, whatabout that. oh nobody
knows, oh! oh!

These are private addresses. The only thing that the registry is
undertaking that matters at IETF level is that there won't be duplicates.
And every registry customer is going to be able to verify that their
assignment is unique at the time it is assigned just by checking the
registry. So I have it all covered.

The whole log is going to be public. In fact that is a big part of my plan
to offload cost.


We really need to get over the worry about allowing people to start stuff.
And especially when it comes to registries. If people have issues they can
state, fine. But we saw what happened when folk decided to get precious
about the SRV prefix registry - people just gave up waiting and made them
up. That is what I did for SAML and will do again if necessary.

People need to understand that 'I am starting a project, what code point
can I use' is a request for a code point. It is not a request for
permission to start the project. The Internet is all about permissionless
innovation.