Éric Vyncke has entered the following ballot position for draft-ietf-regext-rdap-rir-search-18: No Objection
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-rir-search/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- # Éric Vyncke, INT AD, comments for draft-ietf-regext-rdap-rir-search-18 CC @evyncke Thank you for the work put into this document. Please find below some non-blocking COMMENT points/nits (replies would be appreciated even if only for my own education). Special thanks to Mario Loffredo for the shepherd's write-up including the WG consensus and some justification of the intended status. Other thanks to Bob Halley, the Internet directorate reviewer (at my request), please consider this int-dir review: https://datatracker.ietf.org/doc/review-ietf-regext-rdap-rir-search-17-intdir-telechat-halley-2025-05-17/ I hope that this review helps to improve the document, Regards, -éric ## COMMENTS (non-blocking) ### Section 3.1 In `rirSearch1`, I guess that the 1 is for a version. It is a little inconsistent with the use of "_0" or "_1" in the relevant IANA registry, moreover other extensions defined in this I-D do not have such versionning. Thus is just puzzling (possibly based on implementations versions). ### Section 3.2.1 It is a little sad to see an IPv4 example in 2025 (the related document, draft-ietf-regext-rdap-geofeed-12, uses IPv6 example). I have appreciated the Figure 3 example though ;-) _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
