Re: [DNSOP] Call for Adoptions: draft-lhotka-dnsop-iana-class-type-yang
Ladislav Lhotka <lhotka@nic.cz> Mon, 22 July 2019 18:12 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 320FF1202F4 for <dnsop@ietfa.amsl.com>; Mon, 22 Jul 2019 11:12:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 FF_b2wtokrdt for <dnsop@ietfa.amsl.com>; Mon, 22 Jul 2019 11:12:51 -0700 (PDT)
Received: from trail.lhotka.name (trail.lhotka.name [77.48.224.143]) by ietfa.amsl.com (Postfix) with ESMTP id 35BE212030D for <dnsop@ietf.org>; Mon, 22 Jul 2019 11:12:51 -0700 (PDT)
Received: by trail.lhotka.name (Postfix, from userid 109) id A29C6182048A; Mon, 22 Jul 2019 20:11:18 +0200 (CEST)
Received: from localhost (dhcp-8bbc.meeting.ietf.org [31.133.139.188]) by trail.lhotka.name (Postfix) with ESMTPSA id 753B6182004A; Mon, 22 Jul 2019 20:11:16 +0200 (CEST)
From: Ladislav Lhotka <lhotka@nic.cz>
To: Petr Špaček <petr.spacek@nic.cz>, dnsop@ietf.org
In-Reply-To: <8de3afb0-374e-b445-5d45-2145168efeb4@nic.cz>
References: <820fe3a1-9d54-15c1-8194-8a607bdf6a31@NLnetLabs.nl> <alpine.LRH.2.21.1907151726520.15898@bofh.nohats.ca> <CADyWQ+Gt7WUjOFP8dMELT+UQLdvPBcMXA4UX2xtZiqtp0zP9nQ@mail.gmail.com> <CAJhMdTNofj4-wjKY1u2B5UhbhbcHYOvr_-V2bfuMK+d9SjHgsA@mail.gmail.com> <ac31455a-e66e-be04-f4d6-6411e896e589@pletterpet.nl> <8de3afb0-374e-b445-5d45-2145168efeb4@nic.cz>
Date: Mon, 22 Jul 2019 14:12:40 -0400
Message-ID: <87v9vu2b1j.fsf@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/eI2nR5p1ER6i4yJea42yqm-2kgc>
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: Mon, 22 Jul 2019 18:12:56 -0000
Petr Špaček <petr.spacek@nic.cz> writes: > On 16. 07. 19 10:03, Matthijs Mekking wrote: >> On 7/16/19 1:49 AM, Joe Abley wrote: >>> On Jul 15, 2019, at 19:13, Tim Wicinski <tjw.ietf@gmail.com> >>> wrote: >>> >>>> Also, the current draft enumerates DLV which needs to be >>>> removed. >>> >>> Can you explain this? >>> >>> I can understand a forthcoming clarification on the use of DLV >>> that might make it ill-advised to publish such an RRType, but >>> it's not obvious that a dictionary of once-used RRTypes in any >>> particular format is useless (for example in understanding >>> observed RRTypes in order to track the length of a deprecated >>> type's tail). >>> >>> Are archaic English worlds redacted from dictionaries? >> This may be my fault: I had put text in >> draft-mekking-dnsop-obsolete-dlv that the DLV reference in this >> draft should be removed. But you are right, the reference to >> DLV can stay in draft-lhotka-dnsop-iana-class-type-yang, just >> like there is a reference to A6. The status of A6 in this >> draft is set to obsolete, as it should be. But what should the >> status of DLV be in this document? This question I guess proves >> Paul's argument that putting snapshots of IANA registries in an >> I-D is a bad idea. > > Ladislav Lhotka, the primary author of the draft and our YANG > expert is not reachable till beginning of IETF, so I will try > reply non-authoritatively to this concern: Thanks, Petr, I can only second what you wrote below. Specifically, the idea is *not* to update the RFC after every change in the IANA registry. As an example, take the iana-if-type module: https://www.iana.org/assignments/iana-if-type/iana-if-type.xhtml Note that the latest revision is 2019-07-16 whereas the revision that appeared in RFC 7224 is 2014-05-08. It might be better to free IANA from this additional burden, but unless we find a better mechanism, I see this as the only only way how parameters from IANA registries can be used in YANG modules. Lada > > Purpose of draft-lhotka-dnsop-iana-class-type-yang-02 is to > establish relationship between existing IANA registries (for DNS > classes and types) and their coresponding YANG modules, and to > and instruct IANA to update the respective YANG module when IANA > DNS registries are updated. > > Last two paragraphs from Introduction: >> This document is a first step in translating DNS-related >> IANA registries to YANG. It contains the initial revision >> of the YANG module "iana-dns-class-rr-type" that defines >> derived types for the common parameters of DNS resource >> records (RR): class and type. These YANG types, "dns-class" >> and "rr-type", reflect the IANA registries "DNS CLASSes" and >> "Resource Record (RR) TYPEs" [IANA-DNS-PARAMETERS]. >> >> It is worth emphasizing that the role of the DNSOP Working >> Group is only in preparing and publishing this initial >> revision of the YANG module. Subsequently, whenever a new >> class or RR type is added to the above registries, IANA will >> also update the iana-dns-class-rr- type YANG module, >> following the instructions in Section 4 below. > > Having said that, I do not understand the concerns expressed > above. > > What exactly are you objecting to? > > That the RFC will contain initial state of the registries (at > time of publication)? > > Or that IANA will automatically update the YANG module from > other registries? > > Please clarify your concerns, I'm lost. Thank you. > > -- Petr Špaček @ CZ.NIC > > _______________________________________________ DNSOP mailing > list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop -- Ladislav Lhotka Head, CZ.NIC Labs PGP Key ID: 0xB8F92B08A9F76C67
- [DNSOP] Call for Adoptions: draft-lhotka-dnsop-ia… Benno Overeinder
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Paul Wouters
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Paul Wouters
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Tim Wicinski
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Joe Abley
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Matthijs Mekking
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Petr Špaček
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Tony Finch
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Ladislav Lhotka
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Ladislav Lhotka
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Normen Kowalewski
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Normen Kowalewski
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Pieter Lexis
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Ladislav Lhotka
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Normen B. Kowalewski
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Benno Overeinder
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Paul Wouters
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Ladislav Lhotka
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Normen Kowalewski
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Bob Harold
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Normen Kowalewski
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Ladislav Lhotka
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Paul Wouters
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Paul Wouters
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Ladislav Lhotka
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Ladislav Lhotka
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Paul Wouters
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Paul Wouters
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Ladislav Lhotka
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Joe Abley
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Ladislav Lhotka
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Paul Wouters
- Re: [DNSOP] Call for Adoptions: draft-lhotka-dnso… Benno Overeinder