Last Call Review of draft-ietf-regext-rdap-partial-response-12
review-ietf-regext-rdap-partial-response-12-genart-lc-schinazi-2020-07-24-00
| Request | Review of | draft-ietf-regext-rdap-partial-response |
|---|---|---|
| Requested revision | No specific revision (document currently at 16) | |
| Type | Last Call Review | |
| Team | General Area Review Team (Gen-ART) (genart) | |
| Deadline | 2020-08-14 | |
| Requested | 2020-07-24 | |
| Authors | Mario Loffredo , Maurizio Martinelli | |
| Draft last updated | 2020-07-24 | |
| Completed reviews |
Genart Last Call review of -12
by
David Schinazi
(diff)
Opsdir Last Call review of -13 by Joel Jaeggli (diff) Secdir Last Call review of -13 by Joseph A. Salowey (diff) |
|
| Assignment | Reviewer | David Schinazi |
| State | Completed | |
| Review |
review-ietf-regext-rdap-partial-response-12-genart-lc-schinazi-2020-07-24
|
|
| Posted at | https://mailarchive.ietf.org/arch/msg/gen-art/YZVkQjNzoOFqURv3nB91kms5XOc | |
| Reviewed revision | 12 (document currently at 16) | |
| Result | Ready with Issues | |
| Completed | 2020-07-24 |
review-ietf-regext-rdap-partial-response-12-genart-lc-schinazi-2020-07-24-00
I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please treat these comments just like any other last call comments. For more information, please see the FAQ at <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>. Document: draft-ietf-regext-rdap-partial-response-12 Reviewer: David Schinazi Review Date: 2020-07-24 IETF LC End Date: 2020-08-14 IESG Telechat date: Not scheduled for a telechat Summary: Document is clear, well-written, and short. Thank you! Major issues: None Minor issues: After reading the document, I was somewhat confused as to the definition of fieldSet query parameter. I think adding a few sentences to Section 2 explaining that a field set is a string that the server generates which maps to a set of fields only known to the server would help. Additionally, specifying that the string can't be empty and which characters are allowed might help avoid interop issues down the road. Nits/editorial comments: None