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

Re: Proposed Agenda: RDRS Standing Committee Agenda 21 October 17:30 UTC
by Eleeza Agopian Oct. 17, 2024

Oct. 17, 2024

Hi Paul and SC members, Allow me to respond on behalf of the org regarding Paul’s question. I am filling in for Lisa Carter as ICANN org’s liaison, as Lisa is on a well-deserved vacation this week and next. We’d like to revisit the discussion regarding Metrics 18 and 19 and the presentation of data with the standing committee. As such, I think the action items about which Paul raised questions will be addressed during that discussion. Many thanks for your patience, Eleeza From: Paul McGrady via Gnso-rdrs-sc <gnso-rdrs-sc(a)icann.org> Reply-To: Paul McGrady <paul(a)elstermcgrady.com> Date: Thursday, October 17, 2024 at 7:25 AM To: Feodora Hamza <feodora.hamza(a)icann.org>, "gnso-rdrs-sc(a)icann.org" <gnso-rdrs-sc(a)icann.org> Subject: [Gnso-rdrs-sc] Re: Proposed Agenda: RDRS Standing Committee Agenda 21 October 17:30 UTC Thanks Feodora. I did not receive a response to my email on pushing back against the homework of writing to each other about ICANN being transparent on the aggregated country requestor data. Do you intend to respond to that? Or, is your plan to address it in item 2 in the agenda? Thanks in advance for communicating where you are on this. Best, Paul From: Feodora Hamza via Gnso-rdrs-sc <gnso-rdrs-sc(a)icann.org> Sent: Thursday, October 17, 2024 7:00 AM To: gnso-rdrs-sc(a)icann.org Subject: [Gnso-rdrs-sc] Proposed Agenda: RDRS Standing Committee Agenda 21 October 17:30 UTC Dear members of the RDRS Standing Committee, Please find below the proposed agenda for the next meeting. Proposed Agenda: RDRS Standing Committee Agenda 21 October 17:30 UTC 1. Welcome * ICANN Standards of behaviour 1. Pending Action Items 2. GSE Presentation on RDRS Outreach and Engagement 3. Discussion on Vice Chair Selection for RDRS SC 4. ICANN81 Session preparation * SC is invited to suggest topics 1. Update on RDRS to GNSO Council 2. Europol RDRS Webinar Feedback 3. Discussion Metric 18 and 19 4. AOB Kind regards, Feodora and Caitlin 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/> This email originated from outside the firm. Please use caution.

2 1

Proposed Agenda: RDRS Standing Committee Agenda 21 October 17:30 UTC
by Feodora Hamza Oct. 17, 2024

Oct. 17, 2024

Dear members of the RDRS Standing Committee, Please find below the proposed agenda for the next meeting. Proposed Agenda: RDRS Standing Committee Agenda 21 October 17:30 UTC 1. Welcome * ICANN Standards of behaviour 1. Pending Action Items 2. GSE Presentation on RDRS Outreach and Engagement 3. Discussion on Vice Chair Selection for RDRS SC 4. ICANN81 Session preparation * SC is invited to suggest topics 1. Update on RDRS to GNSO Council 2. Europol RDRS Webinar Feedback 3. Discussion Metric 18 and 19 4. AOB Kind regards, Feodora and Caitlin 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 1

RDRS Usage Metrics Report published
by Eleeza Agopian Oct. 15, 2024

Oct. 15, 2024

Dear Standing Committee members, Sending the RDRS monthly metrics report for the period 1-30 Sept. 2024 on behalf of Lisa, who is on a well-deserved vacation. Please see the report here: https://www.icann.org/en/system/files/files/rdrs-usage-metrics-15oct24-en.p…. Many thanks, Eleeza

1 0

Re: [EXTERNAL EMAIL] - Re: Preview of the new RDRS metric for Requestor Location by Country (Metric 18)
by Gabriel Andrews Oct. 15, 2024

Oct. 15, 2024

In the US at least, when we request non Disclosure, there is an expectation that the disclosure can be made after a reasonable period of time, and my fuzzy recollection is that 180 days is common. This applies even in the case of Non-Disclosure Orders from the Court (in which the 180 language is typically baked in, and can be modified at the whim of the judge issuing the order). Extensions are both possible and normal (when warranted). Key takeaway: 180 days is a good starting point, and consider the potential need for extensions if/when warranted. From: Steve Crocker via Gnso-rdrs-sc <gnso-rdrs-sc(a)icann.org> Sent: Monday, October 14, 2024 12:05 AM To: farzaneh badii <farzaneh.badii(a)gmail.com> Cc: gnso-rdrs-sc(a)icann.org Subject: [EXTERNAL EMAIL] - [Gnso-rdrs-sc] Re: Preview of the new RDRS metric for Requestor Location by Country (Metric 18) One aspect that I did not hear during the discussion is whether reporting of confidential queries needs to be done in real time or can be done some time later. I think the usual reason for requesting confidentiality is to avoid tipping off the registrant that an inquiry from law enforcement is being made. It's my impression that it would be ok to reveal this detail sometime in the future. I suspect there's no simple rule, e.g. "after two weeks" but is instead related to the progress of the investigation. That said, I can imagine imposing a rule that says the requesting agency must release the hold at some point. To maintain some degree of discipline, perhaps it would be reasonable to report the total number of confidential inquiries that have not been released. If the number keeps growing, it might be appropriate for someone with access to the underlying data to work with the requestors to make sure they are not forgetting to remove the hold. Thanks, Steve On Mon, Oct 7, 2024 at 11:03 AM farzaneh badii via Gnso-rdrs-sc <gnso-rdrs-sc(a)icann.org<mailto:gnso-rdrs-sc@icann.org>> wrote: Thank you Lisa I just wanted to record the response here: At NCSG we care about and advocate for: 1)law enforcement location to be transparently disclosed 2) the number of requests received from the law enforcement agency in each country. These two requests were received well by the SC and reporting on law enforcement requests location is a normal procedure for many tech corporations. Unfortunately how it has been decided to report and display the data defeats the purpose. In my opinion, the discussion went as follows: NCSG requested that the report include the location of law enforcement requests. Then, other SC members suggested that we also report the location of other types of requests. We agreed to this, but our intention was not for all request types to be aggregated into one bucket with a single report on their location. We specifically argued for the law enforcement request locations to be reported separately, in the interest of transparency. The way it's currently designed defeats that purpose. What we agreed on was for the report to include the location of each request type separately. We were being collegial in agreeing to include the locations of other request types, but we did not intend for that to result in the law enforcement request locations being lost or lumped together with others. Our goal was always for the location of law enforcement requests to be reported visibly and transparently. What we envisioned was a simple chart that clearly states: · X number of requests from Intellectual Property holders came from this country · X number of requests from Law Enforcement came from that country. In our (NCSG) request document, we included examples of how other tech companies do this. We referenced tables that clearly display this type of information to clarify what we meant for ease of use. [Google doc link<https://docs.google.com/document/d/1Lyj-g5y8JLBSf-dHm81Cf_bFDRBEeZ-KgYYy44a…>]. Regarding aggregation, it's important to emphasize that confidentiality of law enforcement requests were carefully considered. We had discussions with the Gabreil to ensure that the way we report law enforcement requests does not violate confidentiality, and they agreed with our approach. Other tech companies and organizations report on law enforcement requests, even when there's only one, and they also comply with privacy laws. Privacy policies should not apply to public bodies that should be held accountable to the public. We need to discuss this further. It is crucial to bring some transparency to the location of law enforcement requests. Transparency is also mentioned in ICANN bylaws. Best regards Farzaneh On Thu, Oct 3, 2024 at 6:21 PM Lisa Carter via Gnso-rdrs-sc <gnso-rdrs-sc(a)icann.org<mailto:gnso-rdrs-sc@icann.org>> wrote: Hello Standing Committee Members, Attached is a sample/preview of Metric 18 which displays the number of requestors by country (Item #1 in the RDRS SC Workbook<https://docs.google.com/spreadsheets/d/1XFK-RCT5Nv-KcNgX4eQunkUKgSI35Yc_nUZ…> “Requestors” tab). As a reminder, how ICANN displays Metric 18 and why it is displayed as shown in the attachment was discussed on the Standing Committee call that took place 9 September 2024. You can also reference the explanation in column (J8) ICANN LOE Notes in the RDRS SC Workbook. We will be discussing this new metric as part of the agenda for our call on Monday, 7 October, so any questions or comments you have can be addressed during the call. Metric 18 will be included in the RDRS Usage Metrics Report published by mid-October. Best, Lisa Carter Sr. Program Manager, Strategic Initiatives ICANN [signature_3827786603] _______________________________________________ Gnso-rdrs-sc mailing list -- gnso-rdrs-sc(a)icann.org<mailto:gnso-rdrs-sc@icann.org> To unsubscribe send an email to gnso-rdrs-sc-leave(a)icann.org<mailto:gnso-rdrs-sc-leave@icann.org> _______________________________________________ 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. _______________________________________________ Gnso-rdrs-sc mailing list -- gnso-rdrs-sc(a)icann.org<mailto:gnso-rdrs-sc@icann.org> To unsubscribe send an email to gnso-rdrs-sc-leave(a)icann.org<mailto:gnso-rdrs-sc-leave@icann.org> _______________________________________________ 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. -- Sent by a Verified [Sent by a Verified sender]<https://wallet.unumid.co/authenticate?referralCode=tcp16fM4W47y> sender

1 0

Preview of the new RDRS metric for Requestor Location by Country (Metric 18)
by Lisa Carter Oct. 13, 2024

Oct. 13, 2024

Hello Standing Committee Members, Attached is a sample/preview of Metric 18 which displays the number of requestors by country (Item #1 in the RDRS SC Workbook “Requestors” tab). As a reminder, how ICANN displays Metric 18 and why it is displayed as shown in the attachment was discussed on the Standing Committee call that took place 9 September 2024. You can also reference the explanation in column (J8) ICANN LOE Notes in the RDRS SC Workbook. We will be discussing this new metric as part of the agenda for our call on Monday, 7 October, so any questions or comments you have can be addressed during the call. Metric 18 will be included in the RDRS Usage Metrics Report published by mid-October. Best, Lisa Carter Sr. Program Manager, Strategic Initiatives ICANN

4 3

RDRS User Experience Interview Questions for ICANN81
by Lisa Carter Oct. 9, 2024

Oct. 9, 2024

Hello Standing Committee, As a follow up to our discussion on 7 October around RDRS User Experience Interviews during ICANN81, I’ve included the original 7 Questions ICANN approved for both registrars and requestors and the additional question Steve recommended adding. Also included below is sample of the information ICANN will share during ICANN81 to promote the interviews. Direct email invitations will be sent to participating registrars and to any requestors who have registered for ICANN81 and agreed to receiving marketing for the meeting. Interviews will take place in Istanbul and remotely for those not attending ICANN81 via Zoom . It would be very helpful if the Standing Committee would share with colleagues that ICANN is conducting these interviews during the week of ICANN81, particularly for those that will not be attending ICANN81 and may want to do an interview via Zoom. Sample RDRS User Interview Information that will be shared during ICANN81 via Flyer, Newsletter and Barker Screens: ICANN Registration Data Request Service (RDRS) team Available for Requestor and Registrar User Experience Interviews during ICANN81: The ICANN RDRS Team manages the day-to-day operations of RDRS, including gathering RDRS user feedback to improve the user experience for requestors (including governments, law enforcement, threat intelligence & incident response communities, intellectual property organizations) and registrars participating in the two-year pilot. The team is available for one-on-one interviews with registrar and requestor organizations or individuals currently using RDRS. We will discuss your experiences with RDRS in the following areas: General Feedback - What’s working? What’s not working? Top 5 suggestions for feature/UI improvements How you/your organization use(s) RDRS and more If you are a requestor or registrar currently using RDRS (e.g. submitting or processing RDRS requests) and are willing to provide your feedback on the system, please schedule an interview with ICANN by sending an email to rdrsfeedback(a)icann.org with the subject line “RDRS Interview” and indicating whether you will be in Istanbul for in-person discussions or participating remotely and available for a Zoom Interview. RDRS User Experience Interview Questions for Requestors & Registrars On average, how many requests for non-public gTLD registration data does your organization submit/process daily using RDRS? Outside of RDRS? Please explain. What aspects or elements of the RDRS, as a system (UI), are working well for you/your organization? Please explain. What aspects or elements of the RDRS, as a system (UI), are presenting challenges? Please explain the challenges. Please describe your experience interacting with the registrar/requestor once the registrar receives the request. What is working? What is presenting challenges? What are your top suggestions (up to 5) for improving the user experience in RDRS for all users? Please explain how these suggestions would help all users of the system. What would a future version of RDRS need to look like for your organization to use RDRS regularly as your primary mechanism for submitting/receiving data disclosure requests? Do you have any other comments/feedback for ICANN that may help improve RDRS? Please explain. Additional Question from the GSNO Standing Committee: Do you see any legal or regulatory things on the horizon that could impact your interest in using RDRS? Thanks Lisa Carter Sr. Program Manager, Strategic Initiatives Internet Corporation for Assigned Names and Numbers (ICANN) Telephone: +1 310 578 8953 Email: lisa.carter(a)icann.org Skype: lisa.carter.icann www.icann.org

1 0

2024-10-07 RDRS Standing Committee - Meeting #18
by Feodora Hamza Oct. 8, 2024

Oct. 8, 2024

Dear members of the RDRS SC, Please find below the main discussion points and action items from this week`s meeting. The next meeting is scheduled for Monday, 21 October at 17:30 UTC. Kind regards, Feodora and Caitlin 2024-10-07 RDRS Standing Committee - Meeting #18<https://community.icann.org/pages/viewpage.action?pageId=347373596> RDRS SC Workbook: https://docs.google.com/spreadsheets/d/1XFK-RCT5Nv-KcNgX4eQunkUKgSI35Yc_nUZ… Pending Ais from previous meeting: AI: Chair to complete and send the letter to the GNSO Council. AI: SC members to check the outreach tracker and final report tab for their input. New AIs from last meeting: AI: ICANN Org to share the finalized interview questions with the Standing Committee, incorporating the suggestions proposed by the SC member. AI: ICANN Support Staff to add to the Finding Tab that details about future versions of RDRS to include language to participants that participation. AI: SC members to draft a detailed response to ICANN Legal clarifying the need for more detailed transparency in law enforcement requests by country, in line with NCSG’s original request. AI: ICANN Org to revisit criteria for displaying requestor country data, particularly for law enforcement, and provide clearer justification on thresholds once the detailed response from SC members is received. AI: ICANN to confirm whether an SC member can participate in the Europol training for RDRS and confirm back to the SC. AI: Gabriel Andrews to check availability for participation in Europol's closed event as a representative from the Standing Committee, if permitted. AI: Farzaneh Badii to coordinate with NCSG and confirm whether they will present a section regarding registrants’ protection and their perspective on RDRS in the RDRS User Experience section of the Prep Week presentation. 1. Welcome & Opening Remarks 2. Action Items Follow Up * Impressions Document Update: The document is now referred to as the "Workbook," and a few pending action items remain from earlier sessions. * The outreach tracker (events, meetings, webinars) is ongoing. * Surveys with the DRs and users will take place during ICANN 81. * Outstanding actions include a letter to the GNSO Council, which remains with the Chair for follow-up. AI: Chair to complete and send the letter to the GNSO Council. AI: SC members to check the outreach tracker and final report tab for their input. 3. ICANN 81 a. Session Planning * Discussion about the upcoming ICANN 81 meeting: * Multiple sessions on RDRS are planned, including a session dedicated to outreach and reporting on RDRS progress and a RDRS SC working session for internal discussions. * The registrars will not have a dedicated session for RDRS at this ICANN event, unlike in Kigali. However, Roger confirmed that the registrars will provide input prior to the event. 1. RDRS User Experience Interviews at ICANN 81 * User Experience Interviews: ICANN plans to conduct in-person interviews with requesters and registrars attending ICANN 81. * These interviews will focus on the users’ experience with the RDRS, challenges, improvements, and suggestions. Remote interviews will be available via Zoom for parties not available during ICANN81. * ICANN Org plans will send a copy of the original 7 survey questions to the SC along with the suggested question from Steve Del Biancout from the committee, ensuring they are concise and focused on improving the system. Keeping list of questions short in order to keep interviews conversational. * Steve DelBianco's Suggestion: Add a question “Do you see any legal or regulatory things on the horizon that could impact your interest in using RDRS?” * Concerns were raised about directly contacting requesters, but ICANN Legal clarified the restrictions on communication without explicit consent. * SC members the discussed the need to document that a future version of RDRS needs to include language to participants that participation is RDRS means they are agreeing to be contacted by ICANN for feedback AI: ICANN Org to share the finalized interview questions with the Standing Committee, incorporating the suggestions proposed by the SC member. AI: ICANN Support Staff to add to the Finding Tab that details about future versions of RDRS to include language to participants that participation is RDRS means they are agreeing to be contacted by ICANN for feedback 5. Metric 18 - Requestor Location by Country * Current Status: A preview of Metric 18 was shared, showing a breakdown of requestor countries. * Concerns were raised by Farzaneh Badii that the data presentation does not meet NCSG’s original request for transparency on law enforcement requests. * The current report aggregates data, but the community is seeking a breakdown by country for law enforcement requests, which is standard practice among tech companies for transparency. * ICANN Legal’s Position: Caution is being exercised due to concerns about confidentiality, even though it is not directly a privacy issue. Low numbers of requests from specific countries are being grouped to avoid identifying parties involved. * Gabe provided a link to a sample transparency report for law enforcement: https://transparencyreport.google.com/user-data/overview?hl=en&user_request… * Discussion Points: * The community emphasized that law enforcement requests need to be transparent, and disclosing country-level data is common practice. * It was reiterated that this data is crucial for understanding RDRS usage and ensuring transparency. AI: SC members to draft a detailed response to ICANN Legal clarifying the need for more detailed transparency in law enforcement requests by country, in line with NCSG’s original request. AI: ICANN Org to revisit criteria for displaying requestor country data, particularly for law enforcement, and provide clearer justification on thresholds once the detailed response from SC members is received. 6. Metric 19 - Jurisdiction * Update: This metric will not be ready until November and will follow a similar format to Metric 18. * The metric was to be reported in the same way as Metric 18 and include the jurisdiction where data is processed for all requesters, not just law enforcement. * The committee will have similar concerns for this metric as with Metric 18 and should provide similar response to ICANN to clarify the detailed transparency required so that ICANN can revisit criteria for display this data as well * ICANN pointed out that similar discussion might arise as with Metric 18. * SC members can include in their response to ICANN Legal the same clarification for the need for more detailed transparency for law enforcement. 7. AOB * ICANN & Europol Webinar: Scheduled for 14 October, this event is closed and for Europol only. ICANN Org is checking to see if Standing Committee members, like Gabriel, can attend. AI: ICANN to confirm whether an SC member can participate in the Europol training for RDRS and confirm back to the SC. AI: Gabriel Andrews to check availability for participation in Europol's closed event as a representative from the Standing Committee, if permitted. * Prep Week Webinar: Scheduled for 30 October, presentations will cover: * Registrar presentation by Reg from Tucows. * Requester presentation by John Mcilwain (with potential contributions from NCSG). * Farzaneh Badii requested a brief slot for NCSG to discuss their perspectives on registrants and system protection. AI: Farzaneh Badii to coordinate with NCSG and confirm whether they will present a section regarding registrants’ protection and their perspective on RDRS in the RDRS User Experience section of the Prep Week presentation. * Global Stakeholder Engagement (GSE) Presentation: A session with the GSE team is planned for 21 October, focusing on their engagement efforts and upcoming webinars and training related to RDRS. 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 1

Post call | RDRS Standing Committee | Monday, 07 October 2024
by Julie Bisland Oct. 7, 2024

Oct. 7, 2024

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

1 0

Meeting Invitation | RDRS Standing Committee | Monday, 21 October 2024
by Julie Bisland Oct. 7, 2024

Oct. 7, 2024

Dear all, The next RDRS Standing Committee call is scheduled for Monday, 21 October 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/HoC0F * Check your time zone: https://tinyurl.com/mvzj8vj6 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, 07 October 2024
by Julie Bisland Oct. 7, 2024

Oct. 7, 2024

**15-MINUTE REMINDER** Dear all, The next RDRS Standing Committee call is scheduled for Monday, 07 October 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/HIC0F * Check your time zone: https://tinyurl.com/mry6nce6 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