[netmod] IANA registries and YANG

Ladislav Lhotka <lhotka@nic.cz> Tue, 19 November 2019 10:09 UTC

Return-Path: <lhotka@nic.cz>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 5FF27120813 for <netmod@ietfa.amsl.com>; Tue, 19 Nov 2019 02:09:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id PuThyhTzaNzr for <netmod@ietfa.amsl.com>; Tue, 19 Nov 2019 02:08:59 -0800 (PST)
Received: from trail.lhotka.name (trail.lhotka.name []) by ietfa.amsl.com (Postfix) with ESMTP id 35FC512008D for <netmod@ietf.org>; Tue, 19 Nov 2019 02:08:59 -0800 (PST)
Received: by trail.lhotka.name (Postfix, from userid 109) id ABE791820463; Tue, 19 Nov 2019 11:11:54 +0100 (CET)
Received: from localhost (dhcp-9c3a.meeting.ietf.org []) by trail.lhotka.name (Postfix) with ESMTPSA id 63867182045D for <netmod@ietf.org>; Tue, 19 Nov 2019 11:11:52 +0100 (CET)
From: Ladislav Lhotka <lhotka@nic.cz>
To: netmod@ietf.org
Mail-Followup-To: netmod@ietf.org
Date: Tue, 19 Nov 2019 18:08:52 +0800
Message-ID: <87pnhonpor.fsf@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/00zmS2OzaMq7Vyb7IsHf-LDTOi4>
Subject: [netmod] IANA registries and YANG
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2019 10:09:01 -0000


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

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