- Gnso-rdrs-sc - lists.icann.org

2024-08-26 RDRS Standing Committee - Meeting #15
by Feodora Hamza Aug. 27, 2024

Aug. 27, 2024

Dear members of the Standing Committee, Please find below the main discussion points and action items from this week`s meeting. The next meeting is scheduled for Monday, 9 September at 17:30 UTC. Kind regards, Feodora and Caitlin 2024-08-26 RDRS Standing Committee - Meeting #15<https://community.icann.org/pages/viewpage.action?pageId=347373590> AI: ICANN Staff to check the feasibility of proposed solutions. AI: ICANN to provide details to SC on the amount of time it takes to get a Metrics Usage report published. AI: ICANN Staff to update Impressions Document accordingly with the agreed enhancements and access limitations. AI: ICANN Staff to update Impressions Document with an LOE for the enhancement request. 1. Welcome * The chair confirmed the agenda and allowed time for additional agenda items. Sarah Wyld indicated she would bring up a new idea during the Any Other Business (AOB) segment. 1. RDRS Usage Metrics Repor<https://www.icann.org/en/system/files/files/rdrs-usage-metrics-15aug24-en.p…>t * Continue discussion on Metric 10/Lookups i. The SC discussed the high number of lookups unrelated to domains sponsored by participating registrars. It was discussed that malformed domain names or non-domain names could generate lookup errors due to the search interface. The user interface triggers it’s first query after typing three characters. If there is a 750 millisecond delay between each additional input for the same domain search, then the system will treat that as a separate search query. The SC discussed how this affects the data and agreed that it should not generate bad data. ICANN confirmed that less than 5% of data shows multiple searches on one word entry which is negligible and also indicated the “Registrar Not Supported” is the best indicator of demand in Metric 10. ii. The difference between successful lookups and actual requests submitted was also discussed. The group offered the potential reasons for users abandoning their requests after identifying a valid domain but not submitting a request (this included comments from SC members that they often search to see if a registrar is participating to inform their teams before actually submitting a request at a later time. Various solutions, such as conducting surveys or focus groups, were proposed to understand user behavior better. However, ICANN indicated that users cannot be contacted for input without their consent as it requires use of PII. AI: ICANN Staff to check the feasibility of proposed solutions. a. Cadence of publishing metrics reports going forward * ICANN staff suggested changing the frequency of publishing metrics reports from monthly to quarterly due to create more efficiency and indicated. that CSV data could still be provided to the Standing Committee monthly, but reports could be published to icann.org quarterly. The SC Chair recommended to continue with the monthly reports until completing a full year, after which the cadence could be reconsidered. AI: ICANN to provide details to SC on the amount of time it takes to get a Metrics Usage report published. 1. Next Round of RDRS Enhancements Ready for ICANN (Impressions Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1XFK-RCT5…>) * Registrar Item 2 & 18 i. Item2: Registrars requested the ability to re-categorize requests, for example, changing a request categorized as law enforcement to a more appropriate category. The SC agreed to proceed with this enhancement, understanding that this would override the original categorization made by the requestor. ii. Item 18: A quick efficiency improvement was suggested where, upon completing a case, the system should automatically return the user to the “Pending” request list rather than staying on the completed case screen. The group agreed to prioritize this improvement. iii. SC discussed the access of the document and agreed to limit the access to SC members only, so no third party can make amendments and SC members will have better ability to navigate the document. AI: ICANN Staff to update Impressions Document accordingly with the agreed enhancements and access limitations. 1. Collecting Standing Committee thoughts for RDRS Final Report (based on charter questions) * The chair mentioned that a new tab had been added to the impressions document to start collecting thoughts for the RDRS final report. * The chair also mentioned that a new tab in the impressions document for tracking outreach activities. 1. AOB · Sarah Wyld proposed an enhancement where the public Registration Data Directory Service (RDDS) response could be displayed within the Naming service portal RDRS persona for Registrars alongside the request. This would help registrars and see if the disclosed data is already publicly available. This suggestion was positively received. AI: ICANN Staff to update Impressions Document with an LOE for the enhancement request. Feodora Hamza Policy Development Support Manager (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +32 496 30 24 15 Email: feodora.hamza(a)icann.org<mailto:feodora.hamza@icann.org> Website: www.icann.org<http://www.icann.org>

1 0

email archive?
by Sarah Wyld Aug. 27, 2024

Aug. 27, 2024

Hi all, We have an old email archive and a new (current) list. Both linked here: https://community.icann.org/pages/viewpage.action?pageId=284950817 The link to the old archives doesn't seem to work, I get a 404 error. > Mailing list archives: https://mm.icann.org/mailman/private/gnso-rdrs-sc/ <https://mm.icann.org/mailman/private/gnso-rdrs-sc/> The new one works great! But sometimes I lose emails and want to refer to the archive. Will access to the old one be repaired? Thank you, -- *Sarah Wyld, CIPP/E* Policy & Privacy Manager Pronouns: she/they swyld(a)tucows.com

2 2

Post call | RDRS Standing Committee | Monday, 26 August 2024
by Terri Agnew Aug. 26, 2024

Aug. 26, 2024

Dear all, The recordings for the RDRS Standing Committee call held on Monday, 26 August 2024 can be found on the agenda wiki page <https://community.icann.org/x/FoC0F> (attendance included) and the GNSO Master Calendar<https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…>. These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom recording (including audio, visual, rough transcript, chat archive) * Presentation displayed during the meeting (if applicable) * Agenda and Notes/Action Items (if applicable) For additional information, you may consult the mailing list archives<https://urldefense.com/v3/__https:/lists.icann.org/hyperkitty/list/gnso-rdr…> and the main wiki page<https://community.icann.org/x/HgH8E>. Thank you! Kind regards, Terri Policy Team Supporting the GNSO

1 0

Meeting Invitation | RDRS Standing Committee | Monday, 09 September 2024
by Terri Agnew Aug. 26, 2024

Aug. 26, 2024

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 09 September 2024 at 17:30 UTC for 60 minutes. To join - Zoom Information: Main Zoom Webinar link: https://icann.zoom.us/j/92181477886?pwd=TlJHTU5EY1d3bUxLV2s3UStPS2MxZz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/92181477886?pwd=TlJHTU5E…> Passcode: Z@S07?t=v5 Audio only option: Webinar ID: 921 8147 7886 Passcode: 3121016458 International numbers available: https://icann.zoom.us/u/acS1yc2A1 <https://urldefense.com/v3/__https:/icann.zoom.us/u/acS1yc2A1__;!!PtGJab4!9A…> Members, alternates, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send apologies to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Wiki agenda page for 2024: https://community.icann.org/x/_YAYEQ * Check your time zone: https://tinyurl.com/2s42rwsp ONLY for Members & Alternates * Please join via the above Zoom Webinar link and staff will promote you to panelist. * Please select “ Everyone” when posting to the chat for everyone to see your chat and so it’s captured in the recording. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

**Starting in 15 minutes | Meeting Invitation | RDRS Standing Committee | Monday, 26 August 2024
by Terri Agnew Aug. 26, 2024

Aug. 26, 2024

**Starting in 15 minutes Dear all, The next RDRS Standing Committee call is scheduled for Monday, 26 August 2024 at 17:30 UTC for 60 minutes. To join - Zoom Information: Main Zoom Webinar link: https://icann.zoom.us/j/92181477886?pwd=TlJHTU5EY1d3bUxLV2s3UStPS2MxZz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/92181477886?pwd=TlJHTU5E…> Passcode: Z@S07?t=v5 Audio only option: Webinar ID: 921 8147 7886 Passcode: 3121016458 International numbers available: https://icann.zoom.us/u/acS1yc2A1 <https://urldefense.com/v3/__https:/icann.zoom.us/u/acS1yc2A1__;!!PtGJab4!9A…> Members, alternates, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send apologies to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Wiki agenda page: https://community.icann.org/x/FoC0F * Check your time zone: https://tinyurl.com/35btje3s ONLY for Members & Alternates * Please join via the above Zoom Webinar link and staff will promote you to panelist. * Please select “ Everyone” when posting to the chat for everyone to see your chat and so it’s captured in the recording. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Devan Policy Team Supporting the GNSO

1 0

REMINDER | Meeting Invitation | RDRS Standing Committee | Monday, 26 August 2024
by Devan Reed Aug. 23, 2024

Aug. 23, 2024

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 26 August 2024 at 17:30 UTC for 60 minutes. To join - Zoom Information: Main Zoom Webinar link: https://icann.zoom.us/j/92181477886?pwd=TlJHTU5EY1d3bUxLV2s3UStPS2MxZz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/92181477886?pwd=TlJHTU5E…> Passcode: Z@S07?t=v5 Audio only option: Webinar ID: 921 8147 7886 Passcode: 3121016458 International numbers available: https://icann.zoom.us/u/acS1yc2A1 <https://urldefense.com/v3/__https:/icann.zoom.us/u/acS1yc2A1__;!!PtGJab4!9A…> Members, alternates, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send apologies to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Wiki agenda page: https://community.icann.org/x/FoC0F * Check your time zone: https://tinyurl.com/35btje3s ONLY for Members & Alternates * Please join via the above Zoom Webinar link and staff will promote you to panelist. * Please select “ Everyone” when posting to the chat for everyone to see your chat and so it’s captured in the recording. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Devan Policy Team Supporting the GNSO

1 0

Proposed Agenda RDRS Standing Committee Meeting on Monday, 26 August
by Feodora Hamza Aug. 22, 2024

Aug. 22, 2024

Dear RDRS Standing Committee Members, Below, please find the proposed agenda for our next meeting on Monday, 26 August at 17:30 UTC. Thank you. Best regards, Feodora and Caitlin == RDRS Standing Committee Meeting on Monday, 26 August 2024 at 17:30 UTC Proposed Agenda 1.Welcome 2. RDRS Usage Metrics Repor<https://www.icann.org/en/system/files/files/rdrs-usage-metrics-15aug24-en.p…>t * Continue discussion on Metric 10/Lookups * Cadence of publishing metrics reports going forward 3. Next Round of RDRS Enhancements Ready for ICANN (Impressions Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1XFK-RCT5…>) * Registrar Item 2 & 18 * Requestor Item 1 4. Collecting Standing Committee thoughts for RDRS Final Report (based on charter questions) 5. AOB Feodora Hamza Policy Development Support Manager (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +32 496 30 24 15 Email: feodora.hamza(a)icann.org<mailto:feodora.hamza@icann.org> Website: www.icann.org<http://www.icann.org>

1 0

Requests with invalid domain names
by Alan Greenberg Aug. 16, 2024

Aug. 16, 2024

I just went through the process. The User Interface does not allow you to hit next and go onto submit info about why you are making the request unless the domain name is properly formed and found to be registered with a participating registrar. So although the various reasons domain names are not acceptable is important, it does not seem to be a subset of the total number of submitted requests. It appears that if you pause typing for a second or so, it will do a lookup and that is what seems to be reported in Metric 10, which is a much higher total than the number of disclosure requests submitted. But that raises another question. Metric 5 is the number of disclosure requests. Metric 6.1 is labeled "Number of times the data request form for non-participating registrars has been used" but in the detailed description says it is the number of time the export PDF function is used. Metric 6.2 is labeled "Number of times the data request form for participating registrars has been used". For June, the numbers were 170, 23 and 87. For the record, Metric 10 was 1,579 which matches the idea that it is counting lookups every time typing pauses (my guess is bots do not pause). 6.1 + 6.2 do not add up to 5. So I presume that the difference is the number of times the someone finished the form for a non-participating registrar but did NOT export the form. Correct? If I have that right, it means that of the 170 requests entered, 87 were for participating registrars and 82 for non-participating registrars. Or am I missing something??? Alan

3 4

Re: The July RDRS Usage Metrics report is published.
by Lisa Carter Aug. 15, 2024

Aug. 15, 2024

Hi All, The RDRS Usage Metrics Report covering 1-31 July has been published to the RDRS page. Thanks. Lisa Carter Sr. Program Manager, Strategic Initiatives ICANN

1 0

Re: 2024-08-12 RDRS Standing Committee - Meeting #14
by Lisa Carter Aug. 14, 2024

Aug. 14, 2024

Hi All, As a follow up on the AOB item in our meeting on Monday, I wanted to provide an update on the concern about incomplete domain inputs affecting domain lookup results for Metric 10. The ICANN team checked the data for Metric 10 and the number of domain lookups that appear to be repetitive input delay is very low (<5%). The data cannot be removed from the metrics as it is part of the system data. Additionally, keeping in mind that RDRS is meant for intake of disclosure requests, even if the lookup number was higher (due to partial entries inflating total lookups overall), lookup data does not give ICANN any actionable feedback on the direction of RDRS as an intake system for disclosure requests. In general, the RDRS metrics are focused on the requests themselves, not the lookups. I hope this is helpful. Thanks Lisa Carter Sr. Program Manager, Strategic Initiatives ICANN From: Feodora Hamza via Gnso-rdrs-sc <gnso-rdrs-sc(a)icann.org> Reply-To: Feodora Hamza <feodora.hamza(a)icann.org> Date: Tuesday, August 13, 2024 at 7:59 AM To: "gnso-rdrs-sc(a)icann.org" <gnso-rdrs-sc(a)icann.org> Subject: [Gnso-rdrs-sc] 2024-08-12 RDRS Standing Committee - Meeting #14 Dear members of the Standing Committee, Please find below the main discussion points and action items from this week`s meeting. The next meeting is scheduled for Monday, 26 August at 17:30 UTC. Kind regards, Feodora and Caitlin ==================================================================================================================== 2024-08-12 RDRS Standing Committee - Meeting #14 Welcome a. The chair welcomed participants, mentioning his new role as the GNSO-GAC liaison b. The agenda was reviewed, and no changes were requested. RDRS Events & Engagement a. The chair raised concerns about RDRS-related events being organised without the involvement of the group. He stressed the importance of the group being informed and involved in such events. b. SC members echoed the concern, emphasising the need for coordination and better engagement with the group. c. ICANN Org explained the current processes, including engagement efforts by ICANN’s Global Stakeholder Engagement (GSE) team. ICANNor mentioned the SC will be notified in advance for future events and proposed that the group could have access to generic presentations and materials to promote RDRS so members can promote RDRS on their own. AI: ICANN org to provide the link to the 8 August North America RDRS Webinar 3. ICANN RDRS Improvement Work Surveys SC chair discussed the low response rates for RDRS surveys and the need for improvements. ICANN Org provided an update on recent changes to the survey request closure email release last week, which has shown an increase in responses since last week. ICANN org mentioned that in-house research experts are working on revamping the survey questions and will share with one or two SC volunteers for review/input. Sarah Wyld volunteered to review the new survey questions after her vacation. AI: ICANN Org to post current survey questions on the Wiki and will post new questions when they are final. AI: ICANN org to post the PDF for the generic RDRS deck and RDRS Flyer to the Wiki RDRS Form ICANN org discussed the need to improve the RDRS form by providing better help text for certain questions to improve data quality. Volunteers were requested to review these proposed enhancements, ideally a registrar and a requester. No volunteers on the call. 4. Next Round of RDRS Enhancements Ready for ICANN(Impressions Document [docs.google.com] Registrar Item 2-Priority 2: Ability for registrars to change request category SC chair noted that not much progress had been made on the improvement items in the absence of key participants. The group agreed to revisit this in the next meeting when all relevant members are present. ICANN Org indicated that the priority 2 feature would function for registrars similar to the way registrars change priority of requests currently. Metrics would be affected in that anytime a registrar changes request category the data for Metric 8 will change accordingly. 5. AOB Metric 10 Review – How the domain search data is parsed for “Domain Not Found”, “Domain Not Supported”, etc. Simon Raveh explained the logic behind various system rules for parsing domain search results and how domains are validated in the RDRS system. Concerns were raised about the accuracy of statistics due to possible misinterpretations of the data (e.g., bots or incomplete domain inputs).However, no final decisions were made. AI: The document presented by Simon explaining the rules for how Metric 10 data is parsed will be posted on the Wiki. Feodora Hamza Policy Development Support Manager (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +32 496 30 24 15 Email: feodora.hamza(a)icann.org Website: www.icann.org

1 0