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

Upcoming RDRS Standing Committee calls
by Devan Reed Nov. 13, 2024

Nov. 13, 2024

**We are sending in advance to get dates on everyone’s calendar. Dear all, The .ics is attached for next 8 calls for the RDRS Standing Committee; dates are listed below. The calls take place at 17:30 UTC for 60 minutes. * Monday, 11 March 2024 (invite has been sent) * Monday, 25 March 2024 * Monday, 08 April 2024 * Monday, 22 April 2024 * Monday, 06 May 2024 * Monday, 20 May 2024 * Monday, 03 June 2024 * Monday, 17 June 2024 You should have received an email invite for the next meeting, 11 March; future invites will be sent out closer to the date of the calls. Thank you. With kind regards, Devan

2 1

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