Re: [netmod] IANA registries and YANG

Martin Bjorklund <mbj@tail-f.com> Tue, 19 November 2019 10:17 UTC

Return-Path: <mbj@tail-f.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A46FA1208B1 for <netmod@ietfa.amsl.com>; Tue, 19 Nov 2019 02:17:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 k8tm4YykQmgE for <netmod@ietfa.amsl.com>; Tue, 19 Nov 2019 02:17:21 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id BC2091208AD for <netmod@ietf.org>; Tue, 19 Nov 2019 02:17:20 -0800 (PST)
Received: from localhost (h-4-44.A165.priv.bahnhof.se [158.174.4.44]) by mail.tail-f.com (Postfix) with ESMTPSA id 43B3D1AE018B; Tue, 19 Nov 2019 11:17:19 +0100 (CET)
Date: Tue, 19 Nov 2019 11:17:19 +0100 (CET)
Message-Id: <20191119.111719.159939836067629500.mbj@tail-f.com>
To: lhotka@nic.cz
Cc: netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <87pnhonpor.fsf@nic.cz>
References: <87pnhonpor.fsf@nic.cz>
X-Mailer: Mew version 6.8 on Emacs 25.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/7jXGwpADTxv28kc8DVt7AOiqJxU>
Subject: Re: [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:17:26 -0000

Ladislav Lhotka <lhotka@nic.cz> wrote:
> 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
> 
> 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.

Do you mean that the RFC editor removes it and the RFC just points to
the IANA registry?  And then the RFC editor hands it over to IANA so
that they can use it as an initial version to be published?

As long as the instructions to the RFC editor are clear, I think this
can work.



/martin


> 
> 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
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>