Hello all, I agree with Tim's point. Support +1 RFC8499 provides the DNS terminology, which provides a list of DNS protocol related terminology. This document can provide a neutral DNS Data Dictionary related to Domain name registered data. I think that it will be useful for registry, registrar and registrant.
One suggestion: RFC8499 is named with "DNS terminology" while this document is named with "DNS Data Dictionary". Just having a quick look at these two names, it seems it is not easy to distinguish between them. How about renaming "DNS Data Dictionary" to "DNS Registration Data Dictionary" or seome else? Best Regard. Jiankang Yao From: Tim Wicinski Date: 2021-12-19 10:36 To: regext Subject: Re: [regext] Request to adopt draft-flanagan-regext-datadictionary-01 REGEXT chairs Please count this as my +1 for adopting this work. I find this highly relevant to not just create this dictionary, but offer precise definitions for terms to avoid any "squishness" which seems to come back to bite up when we least expect it. The work in DNSOP on DNS Terminology is a good example of doing something a little dull provides benefits elsewhere. Tim On Sat, Dec 18, 2021 at 9:39 AM Steve Crocker <st...@shinkuro.com> wrote: We request the REGEXT WG adopt draft-flanagan-regext-datadictionary-01 as a work item. The goal is to establish a IANA registry of data elements that are commonly used in multiple applications that handle registration data. We anticipate this dictionary will be overseen by an IESG-appointed set of experts. The existence of this dictionary will not impose any requirements that all of these data elements will be collected nor that any particular set of these will be made available in response to requests. Rather, the intent here is simply to provide a common list of possible data elements and a publicly visible set of names for the data elements. We expect there will be additions to the dictionary, so the list of data elements in the current draft is most likely not complete. That said, we feel it is useful to move forward with the review and adoption process. If and when other data elements are proposed, they can be included through the usual process. Thank you, Heather Flanagan Steve Crocker Edgemoor Research Institute _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
