March 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

Proposed agenda - RDRS Standing Committee Meeting #4 - Monday, 25 March at 17:30 UTC
by Caitlin Tubergen April 5, 2024

April 5, 2024

Dear RDRS Standing Committee Members, Please find below the agenda for the next meeting of the Standing Committee on Monday, 25 March 2024 at 17:30 UTC. Thank you. Best regards, Feodora and Caitlin -- RDRS Standing Committee Meeting #4 Monday, 25 March 2024 at 17:30 UTC Proposed Agenda 1. Welcome 2. RDRS Usage Report * Overview of Changes from Last Report (ICANN org Support Staff) * Reactions from Standing Committee 1. RDRS Usage Metrics Report Summary Data CSV 2. Privacy/Proxy responses in RDRS (Sebastien's 14 March email – see attached) 3. Denial responses and explanation in RDRS 4. AOB

7 11

2024-03-25 RDRS Standing Committee - Follow Up
by Feodora Hamza April 1, 2024

April 1, 2024

Dear RDRS Standing Committee, Please find below the main discussion points and action items from todays meeting. The next meeting is scheduled for 8 April at 17:30 UTC. Kind regards, Feodora and Caitlin 2024-03-25 RDRS Standing Committee - Meeting #04<https://community.icann.org/pages/viewpage.action?pageId=311230528> Action items and main discussion points 1. Welcome 2. RDRS Usage Report a.Overview of Changes from Last Report (ICANN org Support Staff) b.Reactions from Standing Committee o Metric 9 doesn’t seem to correspond to metric 2 and 3? Number seem not to match. AI: ICANN Org to share concerns with the metrics team to provide more clarification on numbers. o No total number of requests that are rejected. Staff pointed to Metric 10 that answers that question. o Number of participating registrars that received requests per month seems to be not shown in metrics. o Metric 3 and 4 show numbers of new requests made per month – in this case March. AI: ICANN Org to cross-check numbers as the new numbers seem too high for a month. o Metric 8 to 22: Is this self-reported? Or who makes that assessment in terms of requestor categorization? Category is based on request type. o More of the requestors data to be mandatory when submitting a request. Address and Phone number may be requested as mandatory by RrSG (Sarah Wyld will check to ensure all RrSG agrees) in order to make disclosure determination. AI: ICANN Org to investigate the effort for above change (making address and phone number required) and consider data privacy aspects of requesting additional PII. o Does the person creating the ICANN account confirm their Email address? ICANN Org performs Email verification. The Email is not re-verified regularly. Should the latter be reconsidered? 3.RDRS Usage Metrics Report Summary Data CSV · Interest in Sankey graphics to present data. Staff to discuss what is possible. AI: ICANN Org to potentially release a CSV file for members to create individual charts. 4.Privacy/Proxy responses in RDRS (Sebastien’s 14 March email – see attached) o How are requests involving P/P data should be handled? Metric 14 was being treated as the response was publicly available. What was the reasoning? If the answer is Privacy/Proxy is the response “success” or “failure”. There are multiple types of publicly available information. E.g.: We could add subcategories to "Public" as subcategories of "Proxy-Affiliated" and "Proxy-NonAffiliated". o Difficult to assess as the PPSAI discussion is not complete yet. o RDRS has pilot of 2 years. PPSAI might take more time, so SC must find alternative. AI: ICANN Org to help with user guides and additional wording for FAQs. Gather small group from SC to work on these. 5.Denial responses and explanation in RDRS · Explain further “denial- needing more information form requestor”. Pending status. At some point tickets should get closed automatically if requestor doesn’t reply with more information. What should the standardized time frame for “pending” status be? 1 month? More or less? 6.AOB AI: ICANN Org to go through impressions document<https://docs.google.com/document/d/14b6bG1Odmx-pLkTHrLSNiqAA4JCky2bewidHa5Y…> to check for further list of improvements posed by SGs. AI: SC Group is encouraged to add modification requests to that document<https://docs.google.com/document/d/14b6bG1Odmx-pLkTHrLSNiqAA4JCky2bewidHa5Y…> and to prioritize the list of improvements. 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>

3 4

Re: [Gnso-rdrs-sc] Proposed agenda - RDRS Standing Committee Meeting #4 - Monday, 25 March at 17:30 UTC
by Steve Crocker March 25, 2024

March 25, 2024

1 0

Post call | RDRS Standing Committee | Monday, 25 March 2024
by Terri Agnew March 25, 2024

March 25, 2024

Dear all, The recordings for the RDRS Standing Committee call held on Monday, 25 March 2024 can be found on the agenda wiki page<https://community.icann.org/x/QACNEg> (attendance included) and the GNSO Master Calendar [gnso.icann.org]<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://mm.icann.org/mailman/private/gnso-rdrs-sc/> 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, 08 April 2024
by Terri Agnew March 25, 2024

March 25, 2024

Dear all, The RDRS Standing Committee call is scheduled for Monday, 08 April 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…> * 2024 Wiki agenda page: https://community.icann.org/x/_YAYEQ * Check your time zone: http://tinyurl.com/24n534nn ONLY for Members & Alternates * Please join via the above Zoom Webinar link and staff will promote you to panelist. * (Members) 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 14 minutes | Meeting Invitation | RDRS Standing Committee | Monday, 25 March 2024
by Terri Agnew March 25, 2024

March 25, 2024

**Starting in 14 minutes Dear all, The RDRS Standing Committee call is scheduled for Monday, 25 March 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/QACNEg * Check your time zone: http://tinyurl.com/3pwcs94p <https://urldefense.com/v3/__http:/tinyurl.com/3pwcs94p__;!!PtGJab4!6BAFVKLv…> ONLY for Members & Alternates * Please join via the above Zoom Webinar link and staff will promote you to panelist. * (Members) 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, 25 March 2024
by Devan Reed March 22, 2024

March 22, 2024

Dear all, The RDRS Standing Committee call is scheduled for Monday, 25 March 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/QACNEg * Check your time zone: http://tinyurl.com/3pwcs94p <https://urldefense.com/v3/__http:/tinyurl.com/3pwcs94p__;!!PtGJab4!6BAFVKLv…> ONLY for Members & Alternates * Please join via the above Zoom Webinar link and staff will promote you to panelist. * (Members) 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

Re: [Gnso-rdrs-sc] Follow-up on 11 March Standing Committee for System Enhancements - Denial Reasons
by Lisa Carter March 19, 2024

March 19, 2024

Hi Sarah, In response to your comments and questions regarding the requestor’s user experience with RDRS outcomes, specifically in regards to the requestor’s understanding of the denial reasons provided, I’ve drafted a document (see attached) with screenshots to show the following: Registrar’s view in the Naming Services portal RDRS persona when logging a response to the request, specifically when only partial information will be provided ( and the all data is publicly available box is not checked). I’ve also included the full list of denial options that are available to the registrar. The email the requestor receives from the RDRS system after the registrar concludes its review and logs a response in the RDRS system. Requestor’s view in the RDRS system once the registrar has logged its denial response(s) to the request. This include a screenshot of the “History” section where the registrar’s denial reasons and denial explanations are viewed by the requestor. Requestor’s view of the full details of the request in the RDRS system once they have clicked on the “Show Full Details” button (shown in item 3 of the attached document). Thanks Lisa Carter Sr. Program Manager, Strategic Initiatives ICANN From: Lisa Carter <lisa.carter(a)icann.org> Date: Wednesday, March 13, 2024 at 7:29 AM To: Sarah Wyld <swyld(a)tucows.com>, "gnso-rdrs-sc(a)icann.org" <gnso-rdrs-sc(a)icann.org> Subject: Re: [Gnso-rdrs-sc] Follow-up on 11 March Standing Committee for System Enhancements Hi Sarah, Thanks. These are all good comments/questions you pose regarding denial reasons and definitely something we can/should discuss on our next system enhancements call. I will be chatting with our technical team about the functionality question so we can provide the screenshots (and some explanation of system behavior) as we discussed on our call Monday. Thanks Lisa Carter Sr. Program Manager, Strategic Initiatives ICANN From: Gnso-rdrs-sc <gnso-rdrs-sc-bounces(a)icann.org> on behalf of Sarah Wyld <swyld(a)tucows.com> Organization: Tucows Date: Wednesday, March 13, 2024 at 5:59 AM To: "gnso-rdrs-sc(a)icann.org" <gnso-rdrs-sc(a)icann.org> Subject: Re: [Gnso-rdrs-sc] Follow-up on 11 March Standing Committee for System Enhancements Thanks Lisa! As discussed at the meeting, I understand that requestors are not always clear on the outcomes for their requests, it sounds like the denial reasons are not always readily evident. This seems like a significant barrier to a positive user experience, and I think that registrars would be open to improvements re indicating the outcome to the requestors, but we all need more info first. Here are the questions that arise for me: If a registrar selects 'denied' and then selects a reason from the menu, what is shown to the requestor? How is it shown, does the requestor get an email or must they look at it in the RDRS interface? How does the RDRS functionality for indicating outcomes compare to what requestors expect? Should any difference be addressed by modifying what the registrar does in RDRS, or by educating the requestor on RDRS functionality? I know there is an optional box for further explanation, but I would generally expect that the provided menu of options should be enough info, do we need to revisit those and consider enhancements? Thanks, Sarah Wyld, CIPP/E Policy & Privacy Manager Pronouns: she/they swyld(a)tucows.com On 2024-03-11 6:15 p.m., Lisa Carter wrote: Hi All, As promised, here is the list of enhancements I reviewed on our call today. I’m hoping to get back to you toward the end of the week with details on timing for implementation for the items below. System Enhancements for RDRS Requestors discussed on 11 March: Improved error messaging to address concerns surfaced at the EURALO roundtable (e.g. ccTLDs, non-participating registrars, unsupported TLDs) Language added to system interface to indicate which TLDs are not supported in RDRS (e.g. ccTLDs, mil, .int, .arpa, .gov, .edu) The “Help” link on the RDRS requestor home page will be anchored to the “RDRS Resources” section of the RDRS page of icann.org for better user experience RDRS FAQs for Requestors will be updated to include additional explanations on unsupported TLDs (e.g. .mil, .int, .arpa, .gov, .edu) Thanks Lisa Carter Sr. Program Manager, Strategic Initiatives _______________________________________________ Gnso-rdrs-sc mailing list Gnso-rdrs-sc(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-rdrs-sc _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

1 0

RDRS - PP issue response.
by Sebastien＠registry.godaddy March 18, 2024

March 18, 2024

Dear Standing Committee and ICANN Colleagues, Sarah Wyld, John McElwaine and I had a call today to review the issue of responses to Privacy and Proxy. It transpired during the ICANN79 week, on and off mic, that a substantial part of the denials received by Requestors were due to PP, but were not captured in a consistent manner across all responding Registrars. The Standing Committee is not going to resolve the issue of PP; there is a bespoke group looking into it and currently working next steps out between Staff and Council. The SC obviously should not influence Registrars’ balancing test and decisions around disclosure. This said, we agreed that efforts are required into ensure that same outcomes should be returned to the Requestors via the system in same statistically trackable answers. We agree and submit to the Committee that: 1. The gamut of existing available answers exists on the current platform, there is no need to add any PP specific answer. If the registrar is aware that the domain uses a P/P service and will not disclose any further data, they should use the checkbox labelled "If all of the data is publicly available, please check this box" . 2. Requestor FAQ/User Guide should be adapted to clearly indicate that “all data is publicly available” typically refers to a registration under PP which the Registrar is unable to disclose and for which disclosure should be requested directly from the PP provider. 3. Registrar FAQ/User Guide should be adapted to clearly indicate that the “If all of the data is publicly available, please check this box” checkbox should be used in the case of data Requests under known PP which a Registrar cannot disclose directly. 4. In-line tips in the Registrar interface should be added (pop-up additional information, or directly in-line) as a reminder to the same. This is redundant information, but we see it as important to ensure existing Registrars who are not likely to regularly consult the FAQs, be aware of this new guideline. 5. Communicate on the same with Requestor and Registrar communities via already established channels. We look to Staff for help and guidance for items 2, 3 and 4. 5 should be relayed to ICANN Account Managers in charge of participating Registrars. This will neither resolve the issue of PP nor change the level of data disclosure, but aims at: * Offering a clearer answer to requestors, and limit the diversity of answers given to a same issue, * Allowing to more clearly track Requests under PP and avoid having them weighing on disclosure/non-disclosure statistics. We look forward to your comments. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_1782455406] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy>

4 6