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? * 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? * 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. -MSK
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
