Hi folks,
I invite you to consider that, currently, rdap-reverse-search and,
potentially, three other RDAP-related docs are blocked waiting for the
end of this discussion.
In addition, it seems to me more logical, first, to decide how RDAP
exentions must be treated and, then, correct RFC 9083 to make it
consistent with what decided.
Once agreed on which approach to follow, we could proceed in parallel
with the correction of RFC 9083 and the writing of a document defining
the guidelines for extending RDAP.
For the sake of completeness and comprehension, such a document might
include the scenarios Jasdip has described in his analysis.
Best,
Mario
Il 15/06/2022 19:27, Hollenbeck, Scott ha scritto:
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://www.ietf.org/mailman/listinfo/regext
--
Dr. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web: http://www.iit.cnr.it/mario.loffredo
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext