Re: [DNSOP] Call for Adoptions: draft-lhotka-dnsop-iana-class-type-yang

Ladislav Lhotka <lhotka@nic.cz> Fri, 11 October 2019 13:33 UTC

Return-Path: <lhotka@nic.cz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B6F7120073; Fri, 11 Oct 2019 06:33:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M1h-upbfgDkj; Fri, 11 Oct 2019 06:33:40 -0700 (PDT)
Received: from trail.lhotka.name (trail.lhotka.name [77.48.224.143]) by ietfa.amsl.com (Postfix) with ESMTP id E2FFD120090; Fri, 11 Oct 2019 06:33:39 -0700 (PDT)
Received: by trail.lhotka.name (Postfix, from userid 109) id E266418204A9; Fri, 11 Oct 2019 15:36:26 +0200 (CEST)
Received: from localhost (unknown [195.113.220.125]) by trail.lhotka.name (Postfix) with ESMTPSA id 8FD551820046; Fri, 11 Oct 2019 15:36:24 +0200 (CEST)
From: Ladislav Lhotka <lhotka@nic.cz>
To: Paul Wouters <paul@nohats.ca>
Cc: iesg@ietf.org, DNSOP WG <dnsop@ietf.org>
In-Reply-To: <alpine.LRH.2.21.1910100951010.10011@bofh.nohats.ca>
References: <820fe3a1-9d54-15c1-8194-8a607bdf6a31@NLnetLabs.nl> <87sgqy2azd.fsf@nic.cz> <920E9418-4440-46F6-87B7-68CF8B03C408@gmx.net> <C66220A931BC4753B6818DAF898AE2E8@T1650> <426d8bf2-cf28-11f6-4435-08fcaa37e7f5@NLnetLabs.nl> <alpine.LRH.2.21.1910071329420.19930@bofh.nohats.ca> <0A5478B0-BC32-46AA-A915-ABC026D247CA@gmx.net> <CA+nkc8BjHrCF7PO_0RKETcLWhNDDA2M66antFE=xusHcdsVHhA@mail.gmail.com> <93dba67e7c86fe1679f9ca534740c93e7af1eabf.camel@nic.cz> <alpine.LRH.2.21.1910091628450.11081@bofh.nohats.ca> <874l0hrr9c.fsf@nic.cz> <alpine.LRH.2.21.1910100951010.10011@bofh.nohats.ca>
Date: Fri, 11 Oct 2019 15:33:35 +0200
Message-ID: <87h84fo18w.fsf@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/E3H3tDC6wLq_L9zQtLkkSHEs8Hk>
Subject: Re: [DNSOP] Call for Adoptions: draft-lhotka-dnsop-iana-class-type-yang
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Oct 2019 13:33:42 -0000

Paul Wouters <paul@nohats.ca>; writes:

> On Thu, 10 Oct 2019, Ladislav Lhotka wrote:
>
>> They should not actually be reading the RFC but get the latest revision of the module from this page:
>>
>> https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml
>
> You are asking for text to go into an RFC, which you then say they
> (implementors) should not read. Clearly then the text should not go
> into the RFC.

It is true that the RFC is actually intended for IANA. Martin Bjorklund suggested in the NETMOD mailing list that similar RFCs only contain a template for the YANG module rather than a snapshot of the registry.

On the other hand, no syntax is defined for specifying such templates, so providing a registry snapshot as a concrete example seems logical. Moreover, IANA can use the snapshot right away as an initial revision.

...

>
> My suggestion was a link the proper IANA registries, which _are_ updated
> by other RFCs to place things into obsolete/deprecated and receive new
> entries based on other new RFCs.
>
> As you said the implementors need to go to the IANA/YANG module place, a
> link to that would be more useful than including a current snapshot of
> the IANA registries.

I agree but, unfortunately, any proper solution might take quite some time. As a temporary solution, would it be possible to continue with the current draft (in DNSOP WG or elsewhere) provided that it will be emphasized that the RFC is intended primarily for IANA, and that implementors should look for the module at the IANA page? 

Lada

>
> Paul

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