+1
Have just two further notes:
1) Think it would be good to add normative language about partial
matching referencing Section 4.1 of RFC 9082 .
2) Per what is stated in section 4.1 0f RFC9083, the rdapConformance
array in the examples Section 4 should include only the extensions used
in the response.
For sure the response including the ipSearchResults array will never
include the autnumSearchResults array and viceversa ;-)
The same goes for the responses including the links about ips or autnums.
Instead, the help response should include all the extensions implemented.
As a result of this, the first two paragraphs of Section 6 should be
modified as well.
Best,
Mario
Il 27/11/2023 15:51, Antoin Verschuren ha scritto:
The document editors have indicated that the following document is ready for
submission to the IESG to be considered for publication as a Proposed Standard:
RDAP RIR Search
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-rir-search/05/
Please indicate your support or no objection for the publication of this
document by replying to this message on list (a simple “+1” is sufficient).
If any working group member has questions regarding the publication of this
document please respond on the list with your concerns by close of business
everywhere, Monday, 11 December 2023.
If there are no objections the document will be submitted to the IESG.
The Document Shepherd for this document is Mario Loffredo.
Thanks,
Jim and Antoin
REGEXT WG Co-Chairs
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
Dott. Mario Loffredo
Senior Technologist
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
