A few small things: The last call notice refers to the draft as "considered for publication as a Best Current Practice". The draft describes itself as a Standards Track candidate. I believe that's just an error in the last call notice.
[I-D.ietf-regext-rdap-reverse-search] is now RFC 9536. I'd like to see something more in the Security Considerations section that specifically notes how search functionality increases the risk of disclosing information that wasn't explicitly requested. We have this text in RFC 9082: "Search functionality also increases the privacy risk of disclosing object relationships that might not otherwise be obvious. For example, a search that returns IDN variants [RFC6927] that do not explicitly match a client-provided search pattern can disclose information about registered domain names that might not be otherwise available. Implementers need to consider the policy and privacy implications of returning information that was not explicitly requested." Maybe just note that the Security Considerations described in RFC 9082 also apply here. Scott > -----Original Message----- > From: James Galvin <gal...@elistx.com> > Sent: Friday, July 12, 2024 5:18 PM > To: REGEXT Working Group <regext@ietf.org> > Subject: [EXTERNAL] [regext] WGLC: draft-ietf-regext-rdap-rir-search-09 > > Caution: This email originated from outside the organization. Do not click > links > or open attachments unless you recognize the sender and know the content is > safe. > > The document editors have indicated that the following document is ready for > submission to the IESG to be considered for publication as a Best Current > Practice: > > RDAP RIR Search > https://secure-web.cisco.com/1bZSsnQGQmxhBWWisxpA-e7EjLi- > FF0G4N3sfIfipgTWVCmeXwOierTpwOew31D7g3qSZRMxhe_HESJdmm6NBVfl > 9-PQKs8ZX0Z1XihN4BcG-4k6wgMbq05HaLTiUO47a- > ylj0vgXs1JhxgJle21VH7uz0egkUqSAS4RzRaLe7Ebvb8pRM1knYxxX24lySavXliF > ANQlXRmnyX0R5sZhzAQ8a49IDSS2prEKgZcI8RtJ5NJl_5GvZU1G0rmok_UFyg > g8JJMOxd5Aq8_5I4kB6G9TYndwZtR5U8XXJTUGsreM/https%3A%2F%2Fdat > atracker.ietf.org%2Fdoc%2Fdraft-ietf-regext-rdap-rir-search%2F09%2F > > This document has been through WGLC previously. However, a number of > questions arose and changes were made that are considered material and thus > we are proceeding with this additional WGLC. > > Please indicate your support or no objection for the publication of this > document by replying to this message on list (a simple “+1” is sufficient). > > If any working group member has questions regarding the publication of this > document please respond on the list with your concerns by close of business > everywhere, Friday, 2 August 2024. This WGLC has been extended to 3 weeks > because of the IETF120 meeting. > > If there are no objections the document will be submitted to the IESG. > > The Document Shepherd for this document is Mario Loffredo. > > Thanks, > > Antoin and Jim > REGEXT WG Co-Chairs > > _______________________________________________ > regext mailing list -- regext@ietf.org > To unsubscribe send an email to regext-le...@ietf.org _______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
