Andy, I believe we'll need to setup a time to meet to discuss the feedback, since I believe we're talking past each other. I'll take this off the mailing list of coordinate a meeting with the co-editors of draft-ietf-regext-rdap-x-media-type and draft-ietf-regext-rdap-versioning to ensure that they are compatible with each other.
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 3/9/26, 5:01 PM, "Andy Newton" <[email protected] <mailto:[email protected]>> wrote: Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi James, You have interspersed the draft text with your commentary in the same paragraphs, making it difficult to pull apart the draft text you are targeting from your own text. Can you use the line numbered output from the I-D nits tool to quote the draft text: https://secure-web.cisco.com/1n5lSBjS7l10vJxM1_dYHJeQ5_HM4vg8EKNg5kYvzgk4m4NVnV5dNKMFqE2qcuRokzfOOXZC8aGwvavigWJt07P6jX9ba6_3a2D77rSZMk_u2H4ZPAXdhQl3E6QzcG02MP7PANdLwwrdY265EiJRNuuYLIn1c1eG2K3a0kUl5Tos93QbNUG66DIpKkzqAgQx6uz8KFtLh68p4cpwX-DS4HzjSkwxnLVrP_UvwzghWLwM-gCPBAcXGtM7tXz0Kl0zGaTEFFxp6bAohAHnqphT1WurKobUMKEIvQ0O8JiLVdrE/https%3A%2F%2Fauthor-tools.ietf.org%2Fapi%2Fidnits%3Furl%3Dhttps%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2F%24DRAFT_VERSION.txt <https://secure-web.cisco.com/1n5lSBjS7l10vJxM1_dYHJeQ5_HM4vg8EKNg5kYvzgk4m4NVnV5dNKMFqE2qcuRokzfOOXZC8aGwvavigWJt07P6jX9ba6_3a2D77rSZMk_u2H4ZPAXdhQl3E6QzcG02MP7PANdLwwrdY265EiJRNuuYLIn1c1eG2K3a0kUl5Tos93QbNUG66DIpKkzqAgQx6uz8KFtLh68p4cpwX-DS4HzjSkwxnLVrP_UvwzghWLwM-gCPBAcXGtM7tXz0Kl0zGaTEFFxp6bAohAHnqphT1WurKobUMKEIvQ0O8JiLVdrE/https%3A%2F%2Fauthor-tools.ietf.org%2Fapi%2Fidnits%3Furl%3Dhttps%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2F%24DRAFT_VERSION.txt> You can use the webform here if it is easier: https://secure-web.cisco.com/1iOzYVs8K_1X1YXtKif_9mGODozYYTRWoEtVlBWSKDouXT4eUWvyaIE6hCIhGY85vQtBByLbnY8uTAzZOmiRbPSO0h1rhFfJ7lzQUfqv2GQhHNp_mQCk0zOTrsN5WQ_Mf7U2OcMcZ19prdmmrShVB6HbgaRUvaU05l_xs6OSftmsglLv3zRbUYu7JHyQDYImNW57pA7x5f8fsnXIAaQmFb1H3MSrmSHK2t-RA81oeqZFaZ7CeGDN6Q1vEioMCH8r_02HVNR89X8uW1yupLTtnbLE9hf9LMTYoH_axy1ELo-E/https%3A%2F%2Fauthor-tools.ietf.org%2Fidnits <https://secure-web.cisco.com/1iOzYVs8K_1X1YXtKif_9mGODozYYTRWoEtVlBWSKDouXT4eUWvyaIE6hCIhGY85vQtBByLbnY8uTAzZOmiRbPSO0h1rhFfJ7lzQUfqv2GQhHNp_mQCk0zOTrsN5WQ_Mf7U2OcMcZ19prdmmrShVB6HbgaRUvaU05l_xs6OSftmsglLv3zRbUYu7JHyQDYImNW57pA7x5f8fsnXIAaQmFb1H3MSrmSHK2t-RA81oeqZFaZ7CeGDN6Q1vEioMCH8r_02HVNR89X8uW1yupLTtnbLE9hf9LMTYoH_axy1ELo-E/https%3A%2F%2Fauthor-tools.ietf.org%2Fidnits> Let me see what I can pick apart... On 09-03-2026 3:47 PM, Gould, James wrote: > JG3- draft-ietf-regext-rdap-versioning-04 ABNF was updated in Section 3.1 to > address the feedback from you, Andy Newton, Jasdip Singh, Pawel Kowalik, and > Maarten Wullink. The draft-ietf-regext-rdap-x-media-type-05 language "This > parameter is a whitespace-separated list of RDAP extension identifiers (as > would be found in the "rdapConformance" array)." Should be updated to "This > parameter is a whitespace-separated list of RDAP extension identifiers (as > would be found in the "rdapConformance" array) or Extension Versioning > Identifiers, as defined by [I-D.ietf-regext-rdap-versioning] ." This enables > the use of both opaque and maturity versioning in > draft-ietf-regext-rdap-versioning using the “exts_list” parameter in > draft-ietf-regext-rdap-x-media-type. The existing language only supports > opaque versioning. My understanding of Pawel's proposal that we discussed at the hall-way meeting at IETF 124 was that maturity versioning was to have the major number in the extension identifier and there would be no need for expressing the minor because minor revisions are supposed to be backwards compatible. However, looking at versioning-04 there appears to be something complicated going on with maturity versioning. The id "maturity_ext1-2.0" (an example from versioning-04) has a super major, then a major, then a minor. Why isn't it just "maturity_ext1"? (BTW, according to the extensions draft, that should be "maturityExt1"). > JG3-Section B.2 remains in the draft. How does inclusion of that section help > in the clarity of this draft? I view it as the wrong place for guidance on > the use of query parameters in RDAP. That is best suited for > draft-ietf-regext-rdap-extensions. It is there to warn against the problems caused by Section 3.2.1 in versioning-04. -andy _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
