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

Re: [Ext] Re: Follow up question on the mandatory country field
by Lisa Carter June 7, 2024

June 7, 2024

Hi Farzaneh and Sebastian, Thanks for this question. I can clarify Farzaneh’s original ask. On page two of the RDRS system form all of the data elements are already required, including jurisdiction (where the data will be processed if provided by the registrar). The only optional field for law enforcement is the confidentiality box. For the enhancements we will release at the end of June, on page one of the RDRS form we will require address and phone number (Priority 1 for Registrars in the Impressions Document) along with an optional field for organization/affiliation as we discussed previously on our Standing Committee call. The full list of enhancements to be released at the end of June is indicated below. I hope this is helpful. Enhancements to be released at the end of June: Registrar enhancements Priorities 1, 4, 5 in Impressions Document Requestor enhancements increase in character limit from 1000 to 2000. better explanation for what “expedited” means in RDRS UI on page 2 Additional enhancement for page two (which currently brings the user into page two below the 1st question - request category) Adding Terms of Service language on page 2 above where the user selects their request category Thanks Lisa Carter Sr. Program Manager, Strategic Initiatives ICANN From: "Sebastien(a)registry.godaddy" <Sebastien(a)registry.godaddy> Date: Thursday, June 6, 2024 at 7:29 AM To: farzaneh badii <farzaneh.badii(a)gmail.com>, "gnso-rdrs-sc(a)icann.org" <gnso-rdrs-sc(a)icann.org>, Gabriel Andrews <gfandrews(a)fbi.gov>, Lisa Carter <lisa.carter(a)icann.org> Subject: [Ext] Re: [Gnso-rdrs-sc] Follow up question on the mandatory country field Hi Farzaneh, Yes, it is also my understanding that the Requestor Country is about to be made mandatory. This is being done as part of changes the Registrar requested under Item 1 of the Registrar table in the Impressions Document. As you mentioned the full requestor contact form is made mandatory. It is also my understanding that while this could serve as a basis for your report on LEA Requestor provenance, there is a specific “Jurisdiction” field in the LEA sub-form. Any data supplied is captured, but it is not currently a mandatory field and is not included in the changed mentioned above. @Gabriel Andrews – We left it on this list on 7 May, that you would go back to the PSWG to confirm they were comfortable adding reports on numbers of Requests per Jurisdiction. I understand you have an informal agreement/non-objection from them. > Are you able to support making the Jurisdiction field also mandatory? > Are you able to support starting reporting on what we have so far? @Lisa Carter – As always I do not have these forms in front of me, and rely here on what you showed me in Paris. Please correct if I got any of this wrong. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager +33612284445 France & Australia sebastien(a)registry.godaddy From: farzaneh badii via Gnso-rdrs-sc <gnso-rdrs-sc(a)icann.org> Date: Monday, 3 June 2024 at 10:14 PM To: gnso-rdrs-sc(a)icann.org <gnso-rdrs-sc(a)icann.org> Subject: [Gnso-rdrs-sc] Follow up question on the mandatory country field Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Hi SC, Just wanted to check, Sarah mentioned in the chat that the country field was being made mandatory (because address of the requestor is becoming mandatory) Does that apply to the Jurisdiction field for LEA? Best regards Farzaneh

2 2

Follow up question on the mandatory country field
by farzaneh badii June 7, 2024

June 7, 2024

Hi SC, Just wanted to check, Sarah mentioned in the chat that the country field was being made mandatory (because address of the requestor is becoming mandatory) Does that apply to the Jurisdiction field for LEA? Best regards Farzaneh

3 2

2024-06-03 RDRS Standing Committee - Meeting #09
by Feodora Hamza June 4, 2024

June 4, 2024

Dear RDRS Standing Committee, Please find below the main discussion points and action items from yesterday`s meeting. The next meeting will take place during ICANN80 on Monday, 10 June; 08:45 – 10:15 UTC. Kind regards, Feodora and Caitlin AI: ICANN Org to discuss internally if stats regarding number of clicks to submit RDRS requests can be generated. AI: SC to go through impression document and identify the owner of each enhancement suggestion made by other members of their constituency. 1. Welcome 2. ICANN 80 Sessions a.RDRS Standing Committee Work Session [icann80.sched.com]<https://urldefense.com/v3/__https:/icann80.sched.com/event/1dr4c/gnso-rdrs-…> – Monday, 10 June; 08:45 – 10:15 UTC b. CSG Membership Work Session [icann80.sched.com]<https://urldefense.com/v3/__https:/icann80.sched.com/event/1dr2u/gnso-csg-m…> – Monday, 10 June; 11:45 – 13:00 UTC c. Registrars and ICANN: Good RDRS Requests [icann80.sched.com]<https://urldefense.com/v3/__https:/icann80.sched.com/event/1dr3I/gnso-regis…> – Tuesday, 11 June; 08:45 – 10:15 UTC 3. RDRS Usage Metrics Report Follow-up a. April Summary of Data update to correct Metric 15 b. March Summary of Data update to correct Metric 15 i. Data of Metric 15 was transposed and ICANN org went back to correct it. ii. ICANN Org will be publishing a correction of the two reports impacted. iii. ICANN Org will take down the old reports and replace them with the new/corrected versions. iv. The CSV files will also be updated with the corrected numbers for Metric 15. v. Each updated Usage Metrics Report will include language within the document to indicate that Metric 15 has been updated to correct the data. 4. System Enhancements a. Adding Terms of Service language on page 2 reference – June i. There seems to be users who self-identify as Law enforcement even though they are not. ICANN Org used language from the Requestor’s User Guide to notify users that providing misleading information in RDRS or claiming to be law enforcement when they are not is a violation of the Terms of Service. b. Update to the Requestor Type Picklist – release date TBD i. ICANN Org will updaterequestor type picklist to remove “Cybersecurity Incident Response Team” from the list and replace it with “CyberSecurity Team” as it is a request type than an incident response Team. In addition ICANN org will add notation in the Metrics document to indicate the update to the picklist and why “Cybersecurity Incident Response Team” will no longer be tracked. The Metrics will still report on the old data. ii. SC suggested to add a footnote to changed/grouped requestor type explainging “previously part of (inser group type)” to allow for back tracking. iii. SC asked if there has been an attempt to gather user feedback from other user groups like LE, incident response, etc.? ICANN Org responded that no additional outreach to LE was initiated and that the the WHOIS design paper was used in creating the picklist. iv. Chair suggested that due to low numbers of survey response, SC could increase the outreach effort on RDRS. v. SC pointed out that It's been reported that it takes more than 30 clicks to submit a request. SC asked if ICANN Org can you measure? Can you add some instrumentation that measures the number of clicks for each? Submission and accumulate those statistics internally. vi. SC members asked what do we learn, or what would we do with clicks information gathered? AI: ICANN Org to discuss internally if stats regarding number of clicks to submit RDRS requests can be generated. c. Reminder on the Impressions document purpose and handling d. Impressions Document Modification Request i. SC members raised the point of the successor system and where bigger advancements/suggestion would be included to be considered in the future? Decision from SC is still pending on this ii. Chair reminded SC to own suggestions made in the impressions documents even if the suggestions come from other members of each constituency. iii. Chair raised the desire to discuss the impressions documents and prioritization of the suggestions in person at ICANN80. iv. SC asked what is the intention of the document: a. To gather impressions of the system b. Or to provide enhancement suggestions for the system v. SC suggested to add separate column to captureLevel of Effort from ICANN org, a column to provide prioritization number, a column for notes and discussion, and a column to state the status of the suggested enhancement. AI: SC to go through impression document and identify the owner of each enhancement suggestion made by other members of their constituency. e. Sankey re: Gabriel Andrews’ 21-22 email i. There was also a request from SC to update Metric 10 by including actual numbers and percentages for each lookup status for the month and cumulatively since launch. Several members agreed this was a good improvement to implement. 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

Post call | RDRS Standing Committee | Monday, 03 June 2024
by Julie Bisland June 3, 2024

June 3, 2024

Dear all, The recordings for the RDRS Standing Committee call held on Monday, 03 June 2024 can be found on the agenda wiki page <https://community.icann.org/x/TACNEg> (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, 17 June 2024
by Julie Bisland June 3, 2024

June 3, 2024

Reminder: the next time the RDRS SC meets will be during ICANN80, 10 June at 10:45 local time. The next call takes place on 17 June 2024. Dear all, The RDRS Standing Committee call is scheduled for Monday, 17 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/TwCNEg * Check your time zone: http://tinyurl.com/2s4yjkh6 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

**15-MINUTE REMINDER** Meeting Invitation | RDRS Standing Committee | Monday, 03 June 2024
by Julie Bisland June 3, 2024

June 3, 2024

**15-MINUTE REMINDER** 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 [tinyurl.com]<https://urldefense.com/v3/__http:/tinyurl.com/478sm9my__;!!PtGJab4!5AtJk2wQ…> 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