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

Paul Wouters <paul@nohats.ca> Tue, 17 December 2019 16:06 UTC

Return-Path: <paul@nohats.ca>
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 B9964120A51 for <dnsop@ietfa.amsl.com>; Tue, 17 Dec 2019 08:06:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=nohats.ca
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 YUT-w2hGNvp9 for <dnsop@ietfa.amsl.com>; Tue, 17 Dec 2019 08:06:23 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 656801209E7 for <dnsop@ietf.org>; Tue, 17 Dec 2019 08:06:23 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 47cjgJ32HKzFbV; Tue, 17 Dec 2019 17:06:20 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1576598780; bh=/QjptBuVaDS7TPTwylsv+bprR/6UUipa8fB/T/XFg1E=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=d4TIkEwJDCze6Ss8c7hWOAeFYBglwr5hKuiw396ooNWoapH2LJ3WmLItR9K2AtTZy xp8orV+j7fAf2gC1jZGp7FDFcKm1GwD3+E2s7W1P3XouEAdYNKofVaHxS7NXS82p8q XPD227tmzNgjEJdGnhUjzgUIJg34WFEupLsSsZG8=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id 3MYnKzs1-ImD; Tue, 17 Dec 2019 17:06:18 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Tue, 17 Dec 2019 17:06:17 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 2512E6007C4F; Tue, 17 Dec 2019 11:06:17 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 21239308F3; Tue, 17 Dec 2019 11:06:17 -0500 (EST)
Date: Tue, 17 Dec 2019 11:06:17 -0500
From: Paul Wouters <paul@nohats.ca>
To: Ladislav Lhotka <lhotka@nic.cz>
cc: dnsop <dnsop@ietf.org>
In-Reply-To: <e0a3830345ac21ac900555090f450ebcaeedf0f6.camel@nic.cz>
Message-ID: <alpine.LRH.2.21.1912171052570.9646@bofh.nohats.ca>
References: <157658758575.26391.17025511136538671205@ietfa.amsl.com> <e0a3830345ac21ac900555090f450ebcaeedf0f6.camel@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/_9DrTqkGNVG0Awi4zpro1Pfs_hQ>
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:06:29 -0000

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.

> 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.

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?

 	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? :)


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

Paul