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

Re: The first Quarterly RDRS Survey Report is published.
by Lisa Carter May 31, 2024

May 31, 2024

Hi All, The first RDRS Quarterly Survey Report for the reporting period 28 November 2023 – 31 March 2024 has been published to the RDRS page. Thanks Lisa Carter Sr. Program Manager, Strategic Initiatives ICANN From: Lisa Carter <lisa.carter(a)icann.org> Date: Wednesday, May 15, 2024 at 6:59 AM To: "gnso-rdrs-sc(a)icann.org" <gnso-rdrs-sc(a)icann.org> Subject: Re: The April RDRS Usage Metrics report is published. Hi All, The RDRS Usage Metrics Report and CSV for the 1-30 April reporting period have been published to the RDRS page. Thanks Lisa Carter Sr. Program Manager, Strategic Initiatives ICANN

2 3

UPDATED LINK | Please share: ICANN80 Policy Outlook Report is now available
by Terri Agnew May 30, 2024

May 30, 2024

**Updated link below. Dear All, The ICANN80 Policy Outlook Report is now available! https://go.icann.org/outlook80 Happy reading! Kind regards, Terri Policy Team Supporting the GNSO

1 0

Please share: ICANN80 Policy Outlook Report is now available
by Terri Agnew May 30, 2024

May 30, 2024

Dear All, The ICANN80 Policy Outlook Report is now available! http://go.icann.org/gnsobriefing [go.icann.org]<https://urldefense.com/v3/__http:/go.icann.org/gnsobriefing__;!!PtGJab4!-Yi…>. Happy reading! Kind regards, Terri Policy Team Supporting the GNSO

1 0

ICANN80 GNSO Policy Briefing
by Julie Bisland May 28, 2024

May 28, 2024

Dear All, On behalf of the GNSO Team, I am happy to report that the GNSO Policy Briefing for ICANN80 is now available for download at http://go.icann.org/gnsobriefing [go.icann.org]<https://urldefense.com/v3/__http:/go.icann.org/gnsobriefing__;!!PtGJab4!-Yi…>. Happy reading! Best Regards, Julie -- Julie Bisland Policy Operations Sr. Coordinator (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> [signature_2510144026]

1 0

impressions doc - cleanup, and question
by Sarah Wyld May 24, 2024

May 24, 2024

Hi team, I'd like to ask our ICANN staff team to do some housekeeping in the Impressions document. I propose adding columns for the priority and LOE (they can be together as they are so interdependent), status, and notes. Then the info that's in the columns where it does not belong, or in the sidebar comments, can be moved into the appropriate boxes. This will make the sheet easier to read, and means that the tables can be re-sorted by priority, status (move all completed to the bottom), etc. What do you think? I also would like to clarify the specific purpose or audience of the Impressions doc. I thought it was for S.C. Members to submit our impressions so that the group could come to agreement on changes to make in the platform, but I see new input that I understand came from an engagement forum and did not go through this Committee. Is that how we'd like to proceed, with this sheet as sort of a clearinghouse for all the input? Thanks, -- *Sarah Wyld, CIPP/E* Policy & Privacy Manager Pronouns: she/they swyld(a)tucows.com

5 6

Invitation to ICANN80 RDRS Session
by Sarah Wyld May 22, 2024

May 22, 2024

Hello RDRS Standing Committee, *The RrSG is hosting a session at ICANN80 reviewing real (anonymized) example RDRS requests and their outcomes, and we invite you all to attend! * GNSO: Registrars and ICANN: Good RDRS Requests <https://icann80.sched.com/event/1dr3I/gnso-registrars-and-icann-good-rdrs-r…> The first 20 minutes of the session relate to registrar accreditation and membership in the RrSG (so you can be a bit late if needed); the remaining 70 minutes will focus on discussing the balancing test, reviewing the example requests, and understanding why the outcomes were what they were. Instead of a slide deck presentation/audience format there will be round tables which we hope will facilitate and encourage open conversation within smaller groups. This session does unfortunately conflict with a GAC Whois session, but we hope that Standing Committee members and other interested people will be able to join us. Thanks, -- *Sarah Wyld, CIPP/E* Policy & Privacy Manager Pronouns: she/they swyld(a)tucows.com

1 0

RDRS Standing Committee Meeting Monday, 20 May 2024 at 17:30 UTC
by Feodora Hamza May 22, 2024

May 22, 2024

Dear RDRS Standing Committee, Please find below the main discussion points and action items from Monday`s meeting. The next meeting is scheduled for 3 June at 17:30 UTC. Kind regards, Feodora and Caitlin RDRS Standing Committee Meeting Monday, 20 May 2024 at 17:30 UTC Agenda Action Item: ICANN Org to take a look at the response time numbers and get back to SC. Action Item: ICANN Org reminded SC to prioritize requestor and registrar enhancement requests by number (1,2,3,4) in the Impressions Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/14b6bG1Odmx-p…>. Action Item: ICANN Org reminded SC to prioritize requestor and registrar enhancement requests by number (1,2,3,4) in the Impressions Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/14b6bG1Odmx-p…>. 1. Welcome 2. Contracted Party Summit RDRS Update & Registrar Experiences Session * Metrics and Enhancements Suggestions During the CP Summit Rrs asked the following questions: 1. How many requests were made for ccTLDs? 2. How many lookups are duplicates? 3. How many Rr did receive requests and which one did not? 4. Who is the requestor? There are users who don’t provide their actual – individual name on request but only company name, which leads to processing delays. Per registrars, the person receiving the data has to be known, it can’t just be a company name. It has to be attributable 2. Other Comments/Feedback 1. Is it possible to deny requests directly in the system? 2. Expedited request…more guidance for requestors will be provided in the UI with next round of enhancements (Expedited does not equal urgent request) 3. UI makes expedited requests are not highlighted in any way in RDRS for registrars processing requests. 4. PGP Encryption does not integrate easily with registrar system, but does allow the registrar to receive the full request via email. 3. RDRS Usage Report<https://www.icann.org/en/system/files/files/rdrs-usage-metrics-15may24-en.p…> 1. Comments/Reactions from Standing Committee * Page 4 says that for the month of April the average response. Time was 6.7 3, but overall 14 9, and based on the table below and the reporting. This seemed confusing for SC. Action Item: ICANN Org to take a look at the numbers and get back to SC. * SC wants to further discuss what is causing a denial, or what is causing requests to take longer to be approved. * Metric 15: How is processing time calculated for requests? RrSG mentioned that when Rr asks the requestor to provide further information, the processing time calculation continues to make it appear that Rrs are taking a long time to process the request even though the action may be back with the requestor. This might lead to longer processing times on paper than in reality. There is currently no way to distinguish in RDRS whether Rr and Requestor has an action to take. * ICANN Org explained that solving the above might need a major change to the system that might be difficult to implement at this stage. 4. System Enhancements Release Update 1. Registrar Enhancements i. Priorities 1, 4, 5 in Impressions Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/14b6bG1Odmx-p…> a. SC asked for Country/Location of requestor to be added as mandatory field for RDRS requests. Address, including country field will be required as part of the next release of enhancements. Action Item: ICANN Org reminded SC to prioritize requestor and registrar enhancement requests by number (1,2,3,4) in the Impressions Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/14b6bG1Odmx-p…>. 1. Requestor Enhancements i. Increase in character limit from 1000 to 2000 ii. Better explanation of what “expedited” means in RDRS UI ICANN Org will release enhancements after ICANN 80 and the end of June. ICANN Org has indicated “level of effort (loe)” for each priority to show feasibility of enhancement request. Action Item: Chair of SC called for SC to provide arguments for ICANN to invest further resources in RDRS “high level of effort” enhancement request. 5. AOB * Sankey Graphic * Discussion on ICANN80 sessions * 2 sessions on RDRS will take place during ICANN80 * 1 session will focus on use cases of RDRS requests by RrSG * 1 session will discuss the user experience with RDRS by CSG 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

Re: The April RDRS Usage Metrics report is published.
by Lisa Carter May 22, 2024

May 22, 2024

Hi All, The RDRS Usage Metrics Report and CSV for the 1-30 April reporting period have been published to the RDRS page. Thanks Lisa Carter Sr. Program Manager, Strategic Initiatives ICANN

4 4

Post call | RDRS Standing Committee | Monday, 20 May 2024
by Julie Bisland May 20, 2024

May 20, 2024

Dear all, The recordings for the RDRS Standing Committee call held on Monday, 20 May 2024 can be found on the agenda wiki page <https://community.icann.org/x/SgCNEg> (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://lists.icann.org/hyperkitty/list/gnso-rdrs-sc@icann.org/> and the main wiki page<https://community.icann.org/x/HgH8E>. Thank you! Kind regards, Julie Policy Team Supporting the GNSO

1 0

Meeting Invitation | RDRS Standing Committee | Monday, 03 June 2024
by Julie Bisland May 20, 2024

May 20, 2024

Dear all, The RDRS Standing Committee call is scheduled for Monday, 03 June 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/TACNEg * Check your time zone: ttp://tinyurl.com/478sm9my<http://tinyurl.com/478sm9my> 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, Julie Policy Team Supporting the GNSO

1 0