Re: [netmod] IANA registries

Kent Watsen <> Mon, 21 October 2019 14:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 398931208B6 for <>; Mon, 21 Oct 2019 07:54:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Y3rlNvEjjrxG for <>; Mon, 21 Oct 2019 07:54:05 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E8DD1120124 for <>; Mon, 21 Oct 2019 07:54:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw;; t=1571669643; h=Content-Type:Content-Transfer-Encoding:From:Mime-Version:Subject:Date:Message-Id:References:Cc:In-Reply-To:To:Feedback-ID; bh=MTOA/ZNWbLQqYQUoTYX9bvRwTkmjiI9Wts8G6WdDvjs=; b=Gv+9kxT8r3womvONYpbMRyO9K+FGmoBM3HEYiANzWTpR4oAcaV9d6aZg/YtUiEG0 kMtEPN0vRzrB8PtWOFBgKQx1vZu+9CvYgYjqGHjF2oN8Cz1zU7x2iCUcrzIE99uZ0DN mi0fF3VLHmkKztsQ/842oAwf9mf0CEC2OJHlxHUI=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Kent Watsen <>
Mime-Version: 1.0 (1.0)
Date: Mon, 21 Oct 2019 14:54:03 +0000
Message-ID: <>
References: <>
Cc: Martin Bjorklund <>, "" <>
In-Reply-To: <>
To: Ladislav Lhotka <>
X-Mailer: iPhone Mail (17A878)
X-SES-Outgoing: 2019.10.21-
Archived-At: <>
Subject: Re: [netmod] IANA registries
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 21 Oct 2019 14:54:10 -0000

Hi Lada, 

> Another option, also suggested in DNSOP WG, was to enable YANG to refer directly to the IANA registry.

For crypto types, I don’t know if this it possible, as there may be many registries involved. 

Regardless, what is it that is doing the referring?  an identityref?  there needs to be a module update, not just a ref, right?  or do you mean that the type is “string” and the values are documented to be from said IANA registries?

> The problem with this is that we have no formalism for writing such templates.


>> How about preparing an initial revision of the module, without writing any RFC, and hand it over to IANA to be published as a
>> supplement to the registry?

I don’t understand.  Can you give a sketch of what you have in mind?