Scott, I believe the first step is to come to consensus on the desired extension registry approach or approaches. I personally like the use of "lunarNIC_level_0" in the rdapConformance to ensure that versioning of the specification is fully supported. Approach B could be used to allow for the registered prefix "lunarNIC" to support the versioned rdapConformance value of "lunarNIC_level_0". Approach C decouples the prefixes from the identifier, so both the prefixes and the versioned identifier would be registered. Updating "lunarNIC_level_0" to "lunarNIC" in RFC 9083 doesn't address the versioning issue.
-- JG James Gould Fellow Engineer jgo...@verisign.com <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgo...@verisign.com> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com <http://verisigninc.com/> On 6/15/22, 1:27 PM, "regext on behalf of Hollenbeck, Scott" <regext-boun...@ietf.org on behalf of shollenbeck=40verisign....@dmarc.ietf.org> wrote: Thanks for doing all this work, Jasdip. Now we have to decide what to do with all of this information. As a first step, I think we need to submit errata to address issues with the existing RFC(s). RFC 9083 uses both "lunarNIC" and "lunarNIC_level_0". At a minimum, Andy and I agree that "lunarNIC_level_0" should be replaced with "lunarNIC". Rationale: Section 2.1 of RFC 9083 describes "lunarNIC" as an example of an identifying prefix and includes examples of this value being used as an extension prefix. Section 4.1 says "For example, if the fictional Registry of the Moon wants to signify that their JSON responses are conformant with their registered extensions, the string used might be "lunarNIC_level_0". We believe that 4.1 and 2.1 are inconsistent and that they can be made consistent by changing "lunarNIC_level_0" with "lunarNIC" in 4.1. Additional errata may be needed. If so, where, and what else needs to be done? Scott _______________________________________________ regext mailing list regext@ietf.org https://secure-web.cisco.com/1YfJ-5LkVa3_5e2919NGv3HEyQy1AoEJ85v6gRz0tFZA0RXar6_Be-zQoFAL0wMeZscZWEZJviAtI80kqxbdAVGXbuyEWNIIHNvaf4rRa-WfawQjzoVSkJsMFmkxcrbEHSLKsRFsj63qrJ8fTXUta2zy5yiiuXzsiQAmJFxKCiJudRDLfaCI_02bRNSDyvOwEWBccERhzp9KGqZgjvPpQrbcCOauHRjWfg-ipxnTEVxEhOAE-djs02lBSoMdQN6nJ/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
