Re: [netmod] IANA registries and YANG

Ladislav Lhotka <> Wed, 18 December 2019 07:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 356471200E0 for <>; Tue, 17 Dec 2019 23:30:03 -0800 (PST)
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, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id yALYjB6NO7Se for <>; Tue, 17 Dec 2019 23:30:01 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id F32C71200D5 for <>; Tue, 17 Dec 2019 23:30:00 -0800 (PST)
Received: by (Postfix, from userid 109) id 542018601A9; Wed, 18 Dec 2019 08:33:31 +0100 (CET)
Received: from localhost (unknown []) by (Postfix) with ESMTPSA id 69CEB8601A3 for <>; Wed, 18 Dec 2019 08:33:30 +0100 (CET)
From: Ladislav Lhotka <>
In-Reply-To: <>
References: <>
Date: Wed, 18 Dec 2019 08:29:58 +0100
Message-ID: <>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <>
Subject: Re: [netmod] IANA registries and YANG
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: Wed, 18 Dec 2019 07:30:03 -0000

Ladislav Lhotka <> writes:

> Hi,
> I would like to discuss the issue of developing YANG modules that mirror IANA registries. The main objection, raised in DNSOP WG in relation to draft-lhotka-dnsop-iana-class-type-yang-02, was that the RFC containing the initial revision of the module doesn't get updated along with the IANA registry (IANA is expected to keep the module in sync without updating the RFC). As a result implementors can use the obsolete snapshot from the RFC.
> I am aware of three solution proposals:
> 1. use some kind of template instead of a YANG module

Followup: template turned out to be the right buzzword! Instead of the initial revision of a YANG module, it is possible to include an XSLT stylesheet and instruct IANA to use it for generating the initial revision of the module directly from the XML version of the registry. I used this approach in

Could this be a recommended way for converting other IANA registries?


> 2. include only two or three entries of the registry as examples so
>    that it is clear that it is not the complete list
> 3. keep the module in the document during the whole I-D stage but
>    instruct the RFC Editor to remove it just before it becomes RFC.
> I am personally in favour of #3. According to Randy Presuhn, who proposed it, this procedure was used during the preparation of BCP 47. It would require some extra coordination with with IANA but, apart from that, it should IMO work well and avoid the problem mentioned above.
> Thanks, Lada
> -- 
> Ladislav Lhotka 
> Head, CZ.NIC Labs
> PGP Key ID: 0xB8F92B08A9F76C67
> _______________________________________________
> netmod mailing list

Ladislav Lhotka 
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67