Last Call Review of draft-ietf-regext-rdap-object-tag-03
review-ietf-regext-rdap-object-tag-03-opsdir-lc-chown-2018-07-15-00

Request Review of draft-ietf-regext-rdap-object-tag
Requested revision No specific revision (document currently at 05)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2018-06-19
Requested 2018-06-05
Authors Scott Hollenbeck , Andy Newton
I-D last updated 2018-07-15
Completed reviews Secdir Last Call review of -04 by Taylor Yu (diff)
Genart Last Call review of -03 by Roni Even (diff)
Opsdir Last Call review of -03 by Tim Chown (diff)
Assignment Reviewer Tim Chown
State Completed
Request Last Call review on draft-ietf-regext-rdap-object-tag by Ops Directorate Assigned
Reviewed revision 03 (document currently at 05)
Result Ready
Completed 2018-07-15
review-ietf-regext-rdap-object-tag-03-opsdir-lc-chown-2018-07-15-00
Hi,

I have reviewed this document as part of the Operational directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written with the intent of improving the operational aspects of
the IETF drafts. Comments that are not addressed in last call may be included
in AD reviews during the IESG review.  Document editors and WG chairs should
treat these comments just like any other last call comments.

This draft extends RFC 7484 to describe an operational (best) practice to allow
Registration Data Access Protocol (RDAP) identifiers to be structured such that
they can convey the authoritative server to use for additional RDAP queries.

The concept of the draft is described well including examples. Two early stage
implementations (Verisign Labs and OpenRDAP) are listed in the document.

The draft is Ready for publication.

One minor nit - the RFC 2119 text should probably be in its own section rather
than within the introduction.