Skip to main content

Last Call Review of draft-ietf-weirds-rdap-query-15
review-ietf-weirds-rdap-query-15-opsdir-lc-banks-2014-10-24-00

Request Review of draft-ietf-weirds-rdap-query
Requested revision No specific revision (document currently at 18)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2014-10-24
Requested 2014-10-12
Authors Andy Newton , Scott Hollenbeck
I-D last updated 2014-10-24
Completed reviews Genart Last Call review of -15 by Brian E. Carpenter (diff)
Genart Last Call review of -15 by Brian E. Carpenter (diff)
Opsdir Last Call review of -15 by Sarah Banks (diff)
Assignment Reviewer Sarah Banks
State Completed
Request Last Call review on draft-ietf-weirds-rdap-query by Ops Directorate Assigned
Reviewed revision 15 (document currently at 18)
Result Has nits
Completed 2014-10-24
review-ietf-weirds-rdap-query-15-opsdir-lc-banks-2014-10-24-00
Hello,
        I've reviewed draft-ietf-weirds-rdap-query-15 for its operational
        impact.

Summary: The document is well written, thorough, provides ample discussion and
examples, and even provides a change log in it's appendix. I have no objections
to this document and believe it should be published

        There are 2 nits from the nits checker for down refs.

        Overall, I found the document very easy to read through, walking
        through the problem it's trying to solve, addressing each add section
        by section, with discussion points for each, and examples for each,
        too. One minor (personal) nit, is the requirement that WHOIS servers
        that don't or can't respond to a request SHOULD return a 501 error
        (RFC7231). In trying to provide some structure, it'd be nice to know
        explicitly that the server has/had an issue responding to the request.
        If the server chooses not to return a 501 in the event of an error,
        then what?

        This aside, the document is ready for publication.

Kind regards,
Sarah