Re: [Lsr] When is an IANA Registry Required

Alvaro Retana <> Wed, 17 March 2021 14:04 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 65F1D3A0C8A; Wed, 17 Mar 2021 07:04:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id W6z8sFMAtepX; Wed, 17 Mar 2021 07:04:20 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::636]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D19AD3A0C87; Wed, 17 Mar 2021 07:04:19 -0700 (PDT)
Received: by with SMTP id c10so2779795ejx.9; Wed, 17 Mar 2021 07:04:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc:content-transfer-encoding; bh=Er4g8tDxaZfq8Zm2Io10QgEQcPo1N4HMfOAGIcuSaTg=; b=h2ADbO6LyXaOsliQuTY/NWRrFkaCMqn7fOgnHbDISlUi+N/W+zSF4Bmy3xPfNp7waA QkCiocCigRjm+VU7so7Ittqy0tQ93cJ9jjw3WtNpd4GDTaJect3LWHYacQ+OWwCcIxmY mRGKS5J0qT6P7/HiZ9ML55Op9UVfhb9WE88acwkQ5eEiQmAxbGAXWSnZvepXtTJH1gjZ E03uBEb+RLD4epYKZzZFMlWu1iPtKWvXiZvXUobvk22S/IIMNwLNPJ/tv5ZHpbZEBpRg PpOmtb7664A5tfJd29WfcYfk/dEsczPaF5WGq0DYWbxVncNEFEOatDlXJBaKT9tj7bRL sMaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc:content-transfer-encoding; bh=Er4g8tDxaZfq8Zm2Io10QgEQcPo1N4HMfOAGIcuSaTg=; b=CIAAXHgqmnNzLnTADhDaVwCrlg0WUngsK7j1K7UwDdtAYMdatiZnpUIoaHxB6Be5fR /RrkE6tUz4NP3AvEZFJ3pmW/rFexxPuiaKURL1UPk68RvisjzBHuHP/79LR11Te/MbBT KZrCcGJNw0R1h3zVGdBFCBvd7a3V1kFh252ybJnFWG4nVNWmfaTSBieDuWGze2WLkr22 wfEPHg2idAPsy/hSmQeDL6jBDk8JD79eodwq/QXBURSQ4O/ynP5fyWvPIq2tTMETwDjL JeH/JC9LG8XhJbVf76SOkomxiqm2ppLCFt626K0KyOg5wQA3cJcKYQzmMAH7f9fIfWtv dEow==
X-Gm-Message-State: AOAM53399tTsNBlPLzy5dcESEfcF5GzJ+8NgQp1Jij+FmEfG8ilp2Y8t O4gjclKeWWFdVcdEm/Laxu9Ufcyik6g84LOkV3k=
X-Google-Smtp-Source: ABdhPJykEY06Tg/OagpTDDBCpznHqRgPB1pimWYizoaFp4A6vuLS1ffFjDWAEViiLNYpEEJ2MW/1gsVIpuJcOn5SyeA=
X-Received: by 2002:a17:906:f0c8:: with SMTP id dk8mr35893723ejb.300.1615989851881; Wed, 17 Mar 2021 07:04:11 -0700 (PDT)
Received: from 1058052472880 named unknown by with HTTPREST; Wed, 17 Mar 2021 07:04:11 -0700
From: Alvaro Retana <>
In-Reply-To: <>
References: <> <> <>
MIME-Version: 1.0
Date: Wed, 17 Mar 2021 07:04:10 -0700
Message-ID: <>
To: "Les Ginsberg (ginsberg)" <>, "" <>
Cc: John Scudder <>, "" <>, "" <>, Christian Hopps <>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [Lsr] When is an IANA Registry Required
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 17 Mar 2021 14:04:22 -0000

On March 16, 2021 at 6:24:22 PM, Les Ginsberg wrote:



> But one thing I find missing in your response is some info on what problem
> YOU think needs to be addressed?

I simply think that the specifications are not complete without
guidance on how to use/assign the unused bits.  I rather try to close
that door before a potential problem may come up.

In the extreme case anyone can make use of the bits, through the ISE
or a different SDO -- ideally we will be paying attention, but may
not.  Sure, a registry doesn't stop implementations from squatting on
codepoints either (even inside the IETF), but at least people have to
want to bypass the allocation rules.

My 1c.