Hi Stewart, Thanks for your review.
On Mon, Feb 24, 2025 at 03:58:52AM -0800, Stewart Bryant via Datatracker wrote: > Reviewer: Stewart Bryant > Review result: Ready > > 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://wiki.ietf.org/en/group/gen/GenArtFAQ>. > > Document: draft-ietf-regext-rdap-rir-search-14 > Reviewer: Stewart Bryant > Review Date: 2025-02-24 > IETF LC End Date: 2025-02-17 > IESG Telechat date: Not scheduled for a telechat > > Summary:The text as written seems fine and could be published once the > comments > from the other reviewers have been addressed. > > That said, I have reviewed it only from a GenART perspective and I am not an > expert on the subtleties of IPv6. > > However ID-Nits raises an interesting question that should be considered. Is > this an IPv4 only protocol. If so then we are done. If it covers IPv6 then the > two questions arise: should there be an IPv6 example and are there any IPv6 > specific issues that need to be addressed. It covers IPv6, because the underlying "ip" endpoint in RDAP supports both IPv4 and IPv6. The specification is in terms of addresses and prefix lengths only, so it will work in the same way for IPv6 as it does for IPv4. We could add IPv6 examples, but because there's no functional difference in how the different types are handled, we don't think it will be of much use to the reader, and the existing IPv4 examples take up quite a bit of space due to the hierarchical nature of the operations. To avoid any potential doubt for readers, we've added the following to the operational considerations section: Although the IP network examples in this document are all in terms of IPv4, the functionality is not specific to IPv4, and servers implementing this functionality must support it for both IPv4 and IPv6 network objects. -Tom _______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
