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

Post call | RDRS Standing Committee | Monday, 01 July 2024
by Julie Bisland July 1, 2024

July 1, 2024

Dear all, The recordings for the RDRS Standing Committee call held on Monday, 01 July 2024 can be found on the agenda wiki page <https://community.icann.org/x/DoC0F> (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 [lists.icann.org]<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, Julie Policy Team Supporting the GNSO

1 0

Metric 10 - Impressions Feedback
by Gabriel Andrews July 1, 2024

July 1, 2024

Requested improvements to Metric 10 have now been included in the impressions document<https://docs.google.com/spreadsheets/d/1XFK-RCT5Nv-KcNgX4eQunkUKgSI35Yc_nUZ…> under line item 20. Edits welcome if my text doesn't match expectations. Drafted text reads as follows. Metric 10 Does not make clear whether TLDs not supported by RDRS were a) ccTLD, b) existent non-contracted non-ccTLDs (.mil, .edu, etc), c) non-existent TLDs ("gibberish"), or other. Revise Metric 10 to make granular, logical disctinctions between TLDs not supported by RDRS. (At minimum, to differentiate between ccTLDs, gibberish, and non-ccTLD non-supported such as .mil/.edu / .gov)

1 0

Revising API Feedback: (via requestors shouldering more of the lift for RDRS API burden)
by Gabriel Andrews July 1, 2024

July 1, 2024

Hi Standing Committee Team, Sebastien: Would you kindly add to the agenda for the next call the discussion topic "API: Revised request to reduce ICANN staff burden / LOE" Having spoken with technical staff on my end, I sense an opportunity to shoulder some of the burden of the "API" request we'd previously assigned a high LoE to. This is taking the tack suggested by Steve Crocker to standardize connections from our end, rather than asking ICANN staff to create new API specific to the RDRS. If we can do this successfully, it might also help inform some important parallel work on issues pertaining to LE identity validation. There would still be an "ask" of ICANN staff, but a much reduced one: 1. We'd want a "test domain" we could use to query to test connections without tainting RDRS data collection. 2. We'd want a little help understanding ICANN's existing API structure > meaning asking ICANN to designating a technical point of contact (email address) that requestor group engineers could send technical q's to if needed. I'm hopeful this could shortcut an otherwise high level of effort ask, and remove a good deal of the burden for it from ICANN shoulders. I seek SC concurrence to bless ICANN staff to take actions 1 & 2 above. -Gabriel PS - Q for clarity: do we know if requestors receive an email from ICANN whenever the "status" of their request changes? I'm told by the engineers this could be relevant (and preferred).

1 1

Meeting Invitation | RDRS Standing Committee | Monday, 15 July 2024
by Julie Bisland July 1, 2024

July 1, 2024

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 15 July 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/EIC0F * Check your time zone: https://tinyurl.com/346mt63r 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, Julie Policy Team Supporting the GNSO

1 0

Letter to Greg DiBiase and Council
by Sebastien＠registry.godaddy July 1, 2024

July 1, 2024

Dear Standing Committee, As discussed on our call last week, please find attached my proposed letter to Greg and Council suggesting/inviting Council or the Requestor+Responder communities directly, to further the more political questions of what constitute requests; allowing to focus on our Pilot Monitoring mandate. Please review and comment. Absent any changes I will send it following our call Monday. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_1642351011] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy>

5 9

**2-MINUTE REMINDER** Meeting Invitation | RDRS Standing Committee | Monday, 01 July 2024
by Julie Bisland July 1, 2024

July 1, 2024

**On in 2 minutes Dear all, The next RDRS Standing Committee call is scheduled for Monday, 01 July 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/DoC0F * Check your time zone: https://tinyurl.com/26w37hwk <https://urldefense.com/v3/__https:/tinyurl.com/26w37hwk__;!!PtGJab4!9skcrnq…> 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, Julie Policy Team Supporting the GNSO

1 0

**15-MINUTE REMINDER** Meeting Invitation | RDRS Standing Committee | Monday, 01 July 2024
by Julie Bisland July 1, 2024

July 1, 2024

**15-MINUTE REMINDER** Dear all, The next RDRS Standing Committee call is scheduled for Monday, 01 July 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/DoC0F * Check your time zone: https://tinyurl.com/26w37hwk <https://urldefense.com/v3/__https:/tinyurl.com/26w37hwk__;!!PtGJab4!9skcrnq…> 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, Julie Policy Team Supporting the GNSO

1 0

REMINDER | Meeting Invitation | RDRS Standing Committee | Monday, 01 July 2024
by Devan Reed June 28, 2024

June 28, 2024

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 01 July 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/DoC0F * Check your time zone: https://tinyurl.com/26w37hwk <https://urldefense.com/v3/__https:/tinyurl.com/26w37hwk__;!!PtGJab4!9skcrnq…> 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, Julie Policy Team Supporting the GNSO

1 0

REMINDER | Meeting Invitation | RDRS Standing Committee | Monday, 01 July 2024
by Terri Agnew June 27, 2024

June 27, 2024

Hello, We are resending invite as it was reported some did not receive this. Thanks! Terri From: Julie Bisland via Gnso-secs <gnso-secs(a)icann.org> Reply-To: Julie Bisland <julie.bisland(a)icann.org> Date: Monday, June 17, 2024 at 2:01 PM To: "gnso-rdrs-sc(a)icann.org" <gnso-rdrs-sc(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Meeting Invitation | RDRS Standing Committee | Monday, 01 July 2024 Dear all, The next RDRS Standing Committee call is scheduled for Monday, 01 July 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/DoC0F * Check your time zone: https://tinyurl.com/26w37hwk [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/26w37hwk__;!!PtGJab4!5MtYcR1…> 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, Julie Policy Team Supporting the GNSO

1 0

2024-06-17 RDRS Standing Committee - Meeting #10
by Feodora Hamza June 27, 2024

June 27, 2024

Dear RDRS Standing Committee, Please find below the main discussion points and action items from last week`s meeting. The next meeting is scheduled for Monday, 1 July at 17:30 UTC. Kind regards, Feodora and Caitlin 2024-06-17 RDRS Standing Committee - Meeting #10<https://community.icann.org/pages/viewpage.action?pageId=311230543> AI: SC Chair to send letter to GNSO Council and inform them about out-of-scope matters regarding RDRS and for them to share with CPH. AI: SC Chair suggested to inquire the GNSO Council about the follow up policy process after the RDRS pilot phase ends. AI: ICANN Org to investigate the possibility to represent integer numbers with percentage of total by month in total for Metric 8. (table on request types) AI: ICANN Org to go ahead and implement that change to metric 10 based on original request. AI: ICANN Org to consider percentage between ccTLD and gTLD request to see if ccTLD inclusion is warranted. AI: ICANN Org to complete the transition of old impressions document into new format by Monday 24 June. AI: SC members to add “ownership” of change request in new impressions document before next meeting. AI: ICANN Org to add additional columns on “impact for successor system”. AI: ICANN Org to consider an additional tap in impressions document for lessons learnt. AI: Chair to check with SC, who will attend on 1st of July? If the participants list is too low, the SC meeting will be moved to the week after. (8 July) 1. Welcome 2. ICANN80 RDRS Sessions Debrief/Discussion * There were 3 sessions taking place during ICANN80 that discussed RDRS * 1 working session, 2 community sessions * Outcome: mostly positive, some misunderstandings have been clarified like the privacy/proxy clarification. * SC members pointed out that some users might be overwhelmed with the terminology used on RDRS to explain the system. * SC members pointed out to some users that explained that their disclosure rate was lower via RDRS than having gone directly to the registrar. * SC members suggested that when we discuss enhancements, we should ask the following questions: Should we do it? And for what benefit? * SC members pointed out that there is a lack of awareness that the RDRS exists. Maybe more outreaches should be done? How are we measuring demand? AI: SC Chair to send letter to GNSO Council and inform them about out-of-scope matters regarding RDRS and for them to share with CPH. AI: SC Chair suggested to inquire the GNSO Council about the follow up policy process after the RDRS pilot phase ends. 1. RDRS Usage Metrics Report * Discuss and agree on the list of new metrics to add to the monthly reports * SC members suggested for Metric 8 that underneath each of the integer numbers in the table. What if we had a percentage of total? AI: ICANN Org to investigate the possibility to represent integer numbers with percentage of total by month in total for Metric 8. (table on request types) · ICANN Org asked for consent regarding change requests related to metric 10 – add the percentages and the number totals by month and since the launch of RDRS. AI: ICANN Org to go ahead and implement that change to metric 10 based on original request. · SC members asked to add percentage between ccTLD and gTLD request to see if ccTLD inclusion is warranted. ICANN will investigate adding this to Metric 10. · SC Chair provided historical reasons why ccTLDs were not included in the RDRS pilot phase. AI: ICANN Org to consider percentage between ccTLD and gTLD request to see if ccTLD inclusion is warranted. · ICANN Org explained there may be a small number of ccTLD requests compared to the gTLD requests. This might not show any significant number in percentage. ICANN org will investigate further and provide update to SC 1. RDRS System Enhancements * Next for Registrars i.Discuss and agree on the next enhancements (Priority 2, 6 & 7?) from the Impressions Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/14b6bG1Odmx-p…> · Next for Requesters i.Discuss and agree on the next enhancements (Priority 1, 2,or 3?) from Impressions Document 1. Update on Impression Document requested changes and management * New design of impressions document has been welcome. * Request by ICANN org for SC to provide all requests for enhancement in the document. AI: ICANN Org to complete the transition of old impressions document into new format by Monday 24 June. · New requests to the impressions document can then be added by SC after that. AI: SC members to add “ownership” of change request in new impressions document before next meeting. · SC members suggested adding an additional column for “impact on successor system”. This would allow a mechanism to make clear that SC is not asking for big issues to be solved within the next 18 months but highlighted that they need to be considered for the successor. AI: ICANN Org to add additional columns on “impact for successor system”. AI: ICANN Org to consider an additional tap in impressions document for lessons learnt. 6. AOB · Follow up on some questions from the Standing Committee on our last call. We did not get to cover this on the call. · Corrected Usage Metrics Reports for March and April have been published · Usage Metrics Report for May will be published this week. AI: Chair to check with SC, who will attend on 1st of July? If the participants list is too low, the SC meeting will be moved to the week after. (8 July) 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>

2 2