I agree with Scott's feedback on the track being changed to Informational and removal of the IANA Registry.
Why doesn't this draft match the approach taken io RFC 8499 for DNS Terminology? The Registration System terms can certainly have overlap with the DNS terms in RFC 8499, where the RFC 8499 reference can be made, but the definition is catered to registration systems. I see value with the terms in RFC 8499 for reference within drafts. I would like to see the same value of terms defined in draft-ietf-regext-datadictionary. The term definitions need to have adequate detail with relevant references made to the registration RFCs (e.g., RFC 5730 - 5733. 9022), which is not currently the case. My recommendation is to refer to this as Registration Terminology instead of Registration Data Dictionary, following the approach taken in RFC 8499 for DNS terminology, and removing the definition of an IANA registry. Thanks, -- JG James Gould Fellow Engineer [email protected] <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[email protected]> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com <http://verisigninc.com/> On 2/14/23, 8:14 AM, "regext on behalf of Hollenbeck, Scott" <[email protected] <mailto:[email protected]> on behalf of [email protected] <mailto:[email protected]>> wrote: I'm aware of two other RFCs that also define terms like this: 4949 (security) and 8499 (DNS). The intended status for this draft is "Standards Track". At best, this should be Informational in the same way that 4949 is informational. Neither of these RFCs creates a registry. As such, I don't see the need for the registry described in Section 3. If a registry is really needed, it would be helpful to include text that describes why the registry is needed. If a case can be made for the registry I'm also confused by the initial assignment described in Section 3.2. It includes a data element "Name", with a reference to Section 2.1 of the draft, but there is no data element "Name" in Section 2.1. Scott _______________________________________________ regext mailing list [email protected] <mailto:[email protected]> https://secure-web.cisco.com/10SGxJBThV6gF8vGi29LMAG0uFCn7qADz6eT8eDTTlNAx_2KL71rgw3tMxntmZ5RctPZjdp27W5frUo1bODZofGGp4FPUXU8ouuO-i3fIHQP26EwvVN4ZV71j3mHTuQ5CQVxI5Hvt_vLF9yy1NA6uRbEn9CNh9PyU_Y3abI0S6d9P1RNDE1FtTGvFoDVbBLlbJpHOAjQTez90BbpcXsi7foA2QSVoBihLvpeTn_CXnigFFQcn5B6pk83GufTYTMcDe8w3D2uJzC1LIsWogLhn6mw9dbtvff0VA0_bo4SN8U0zFTFGdVfFvCu3oTcIU5nA/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext <https://secure-web.cisco.com/10SGxJBThV6gF8vGi29LMAG0uFCn7qADz6eT8eDTTlNAx_2KL71rgw3tMxntmZ5RctPZjdp27W5frUo1bODZofGGp4FPUXU8ouuO-i3fIHQP26EwvVN4ZV71j3mHTuQ5CQVxI5Hvt_vLF9yy1NA6uRbEn9CNh9PyU_Y3abI0S6d9P1RNDE1FtTGvFoDVbBLlbJpHOAjQTez90BbpcXsi7foA2QSVoBihLvpeTn_CXnigFFQcn5B6pk83GufTYTMcDe8w3D2uJzC1LIsWogLhn6mw9dbtvff0VA0_bo4SN8U0zFTFGdVfFvCu3oTcIU5nA/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext> _______________________________________________ regext mailing list [email protected] https://www.ietf.org/mailman/listinfo/regext
