At Mon, 28 Jul 2014 10:17:51 +0200, Matthijs Mekking <[email protected]> wrote:
> >> I have just one very minor comment at this moment. While the draft > >> says in Section 1.2 as follows: > >> > >> A key and signing policy can be expressed in any format. This > >> document uses XML as example. > >> > >> there's only one XML example in it. Actually most examples use YANG. > > > > Thanks for the comment, I have noted it down in an issue [1] and we will > > change it for the next document version. The document was started with > > the current policy data structure used in OpenDNSSEC and that is > > represented in XML, later we switch to YANG so I think there are a few > > more places we need to change the text to reflect that. > > YANG is not used as an example. It is used here as the *modeling* > language for the policy. XML is an example *markup* language that can be > used to write down the policy. Ah, okay. But the current draft looks quite awkward to me even if it's not incorrect, having just one XML example. Hopefully future versions have more XML examples corresponding to each modeling definition. Also, understanding the evolution of the document from full-XML to YANG+XML, it would be more helpful to explicitly clarify YANG is used for modeling. BTW, another minor comment: in Section 2.1.13 the "RollType" leaf node is used, but there's no description for it in the list at the end of the section. I'm not sure if it's intentional, but it generally seems to try to provide a comprehensive list of descriptions, so I guess this is probably overlooked. -- JINMEI, Tatuya _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
