Hi Murray,

thanks a lot for your review and feedback. Please find my comments inline.

Il 10/07/2023 05:22, Murray S. Kucherawy ha scritto:
On Mon, May 15, 2023 at 12:06 PM Antoin Verschuren via Datatracker <nore...@ietf.org> wrote:

    Antoin Verschuren has requested publication of
    draft-ietf-regext-rdap-reverse-search-22 as Proposed Standard on
    behalf of the REGEXT working group.

    Please verify the document's state at
    https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-reverse-search/


Sorry for the delay getting to this.  I think it's in generally good shape.  I've got only a few comments before we can Last Call it:

* In Sections 12.2.3.2 and 12.2.4.2, the individual entries are run together into one big blob.  Could we get blank lines between them, or maybe put each in its own subsection if necessary?  Or make it a table?

[ML] I know that the layout is redundant and not compact at all but it's the only one making the JSONPath expressions quite readable.

I can move the fileds assuming always the same value (e.g. "Related Resource Type", "Registrant Name" and "Registrant Information") at the beginning so that each group of properties related to an entry in the IANA registry gets shorter.

Does it work for you ?


* In Section 13, we have a "REQUIRED" followed by some non-specific advice about what to implement.  This doesn't seem like a good use of BCP 14 key words.  Can we say it some other way?

[ML] Would it be better to use "SHOULD" instead of "are REQUIRED to" ?


* Thanks for including Section 11.

* Section 3 should probably specify what should happen if the JSONpath refers to an attribute/value that's not present in the object it's referencing.

[ML] The JSONPath expressions related to reverse search properties are provided by servers and have been previously registered with IANA, hence they have been checked by Designated Experts. It's very unlikely they are wrong. Can't imagine how clients can operate when servers provide wrong information. I mean, servers can return an error code when clients include wrong or unsupported reverse search properties in thei requests, but servers are always expected to provide correct data.


Best,

Mario


-MSK

_______________________________________________
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

Reply via email to