Re: [DNSOP] I-D Action: draft-ietf-dnsop-iana-class-type-yang-00.txt

Ladislav Lhotka <lhotka@nic.cz> Tue, 17 December 2019 16:34 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 2B475120047 for <dnsop@ietfa.amsl.com>; Tue, 17 Dec 2019 08:34:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.998
X-Spam-Level:
X-Spam-Status: No, score=-6.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 umOHWncrQ7wh for <dnsop@ietfa.amsl.com>; Tue, 17 Dec 2019 08:34:15 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 795AF120A83 for <dnsop@ietf.org>; Tue, 17 Dec 2019 08:34:14 -0800 (PST)
Received: from birdie (unknown [IPv6:2001:1488:fffe:6:a88f:7eff:fed2:45f8]) by mail.nic.cz (Postfix) with ESMTPSA id 9A639140BB4; Tue, 17 Dec 2019 17:34:12 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1576600452; bh=vxMlkUBEH3J+EpSS0n6RFbApvSQMLoBjJCep40rQ1DE=; h=From:To:Date; b=WgJ27wmt8X+AsWL3xCQr9VzOhJpoKiQKPw8Wsx1fHFcHZHzhO5uqnKF7j4p15ohck VELfhBoEeUeA4m/PJHv+/P528ehTsNKe3DG2VwnNr8yp8OZ/7TeRuIG0fbISpZR870 gM24K/ZF72gmDjEkQ2Ysnyt3LYYH6Gn/cPN9F8dg=
Message-ID: <0f388b564d16fb913b04629002a2880fc51637fe.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: Paul Wouters <paul@nohats.ca>
Cc: dnsop <dnsop@ietf.org>
Date: Tue, 17 Dec 2019 17:34:12 +0100
In-Reply-To: <alpine.LRH.2.21.1912171052570.9646@bofh.nohats.ca>
References: <157658758575.26391.17025511136538671205@ietfa.amsl.com> <e0a3830345ac21ac900555090f450ebcaeedf0f6.camel@nic.cz> <alpine.LRH.2.21.1912171052570.9646@bofh.nohats.ca>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.34.2
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.101.4 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/qO8ipMuoAztEaWmbEbickfXXQUo>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-iana-class-type-yang-00.txt
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: Tue, 17 Dec 2019 16:34:18 -0000

On Tue, 2019-12-17 at 11:06 -0500, Paul Wouters wrote:
> On Tue, 17 Dec 2019, Ladislav Lhotka wrote:
> 
> > this draft replaces draft-lhotka-dnsop-iana-class-type-yang-02.
> 
> Although it seems to have no defined that yet in the datatracker. I
> think you can still do it afterwards.

I tried to enter it in the submission form, but the system couldn't find the
individual draft, I don't know why. May I ask our friendly chairs for help?

> 
> > We addressed the previous concerns in that the initial revision of the YANG
> > module is no more included in the document. Instead, the document contains
> > an
> > XSLT 1.0 stysheet that IANA is expected to use for generating the YANG
> > module
> > directly from the DNS Parameters registry.
> 
> This is excellent! Thank you very much for doing this. It prevents
> outdated enumeration in RFCs and links to the IANA registries properly
> and can be used as another example of how to do this properly for other
> IANA registries.

Right. And even if somebody happens to use the stylesheet again in the future,
the result should still correspond to the most recent update of the registry -
except that the revision history won't be present. 

> 
> Some nits:
> 
>  	This document is a first step in translating DNS-related IANA registries
> to YANG.
> 
> If this is only a "first step", what is the second step? That is what is
> missing here and why is it missing?

There is a bunch of other registries on the DNS Parameters page, and more are
elsewhere, such as Domain Name System Security (DNSSEC) Algorithm Numbers.

We would appreciate advice from the DNSOP WG regarding what to do next. For some
registries the conversion to YANG probably makes no sense at all.

> 
>  	The other type, "rr-type-name", is exactly analogical.
> 
> I'm not sure if "analogical" is a common word to use and might be a bit
> confusing to non-native speakers like me. I'm also confused about
> "exactly analogical". What would inexactly analogical be? :)

Being another non-native speaker, I am open to suggestions.

> 
> 
> and "AAAA" type as "TYPE28" -> and the "AAAA" type can be written as "TYPE28"
> 
> they can be used only via their decimal codes -> these can only be specified
> in their decimal values

OK, noted.

Thanks, Ladislav

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