August 2022 - GNSO-Accuracy-ST

RESCHEDULED date and time | Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 25 August 2022 at 15:15 UTC
by Terri Agnew Aug. 16, 2022

Aug. 16, 2022

**As noted on the chairs email to the group a short time ago, the meeting on 18 August 2022 has been rescheduled to 25 August 2022. Please make sure to remove 18 August from your calendars and add on 25 August (note start time) Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 25 August 2022 at 15:15 UTC for 90 minutes. (adjusted start time due to conflict with the GNSO Council call) Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/94504686990?pwd=MWc2eXZE…> Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd <https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, alternates and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests 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…> * Visit the Wiki agenda page: https://community.icann.org/x/uYKLD * Check your time zone: https://tinyurl.com/4pc6udhz ONLY for Members and Alternates * Please join via the above Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and so it is captured in the recording. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form <https://urldefense.com/v3/__https:/forms.gle/GZqMAi4kKDaVP5o66__;!!PtGJab4!…> to communicate who the alternate is replacing and for which period. This information will be publicly posted so that the Team is aware at any time who is active. Alternate Assignment –wiki page<https://community.icann.org/x/-wC7Cg>. 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

1 0

Registration Data Accuracy Scoping Team meeting
by ICANN Policy Calendar Aug. 16, 2022

Aug. 16, 2022

Meeting: Registration Data Accuracy Scoping Team meeting Date/time: Thursday, 25 August 2022 at 15:15 UTC for 90 minutes (start time has been adjusted due to conflict with the GNSO Council call) Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/94504686990?pwd=MWc2eXZE…> Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd <https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, alternates and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests 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…> * Visit the Wiki agenda page: https://community.icann.org/x/uYKLD * Check your time zone: https://tinyurl.com/4pc6udhz ONLY for Members and Alternates * Please join via the above Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and so it is captured in the recording. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form <https://urldefense.com/v3/__https:/forms.gle/GZqMAi4kKDaVP5o66__;!!PtGJab4!…> to communicate who the alternate is replacing and for which period. This information will be publicly posted so that the Team is aware at any time who is active. Alternate Assignment –wiki page<https://community.icann.org/x/-wC7Cg>. 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

1 0

Notes and action items - RDA Scoping Team Meeting #35 - 21 July 2022
by Chantelle Doerksen Aug. 16, 2022

Aug. 16, 2022

Dear RDA Scoping Team Members, Please find below the notes and action items from today’s call. The next RDA Scoping Team call will take place on Thursday, 11 August 2022 at 14:00 UTC for 90 minutes. Best regards, Marika, Berry, and Chantelle -- Action Items In the upcoming days, the staff support team will flag on the mailing list when language has been inserted in relation to a proposed registrar audit (in the next few days) so members can begin reviewing. Scoping team to review write up for assignments #1 and #2 and identify whether there are any remaining “cannot live with items.” If so, please flag these in the form of comments and label these clearly as “cannot live with items.” Minor edits should also be suggested in the form of comments. This review must be completed by Friday 5 August COB at the latest. If groups want to append statements to the write up for assignments #1 and #2, these need to be submitted by Monday, 8 August 23:59 UTC. Policy Support Staff to schedule the next Scoping Team meeting for Thursday, 11 August at 14:00 UTC. Group to provide feedback directly to Steve Crocker on his document outlining the group's consensus on accuracy rules and relationship to the TempSpec. Notes 1. Welcome & Chair Updates Michael and Olga worked with staff to develop a timeline to submit the write up for assignments 1 and 2 to the GNSO Council: Between now and 8 August at the latest, any group can submit a statement regarding the write up for assignments #1 and #2. All submitted statements will be added as an annex to the report. The 11 August call would be used to review statements and resolve any outstanding items with the write up. Shortly after 11 August, the write-up would be submitted to the GNSO Council, ahead of the 15th of August Council document deadline. This would allow the Council to review the write up and especially the recommendations included in the write up. If there is no objection from Council, this could mean that the Scoping Team could potentially commence its work on the implementation of the recommendation(s) during ICANN75. Timeline will be circulated with today’s call notes to the list. 2. Continue review of additional proposals (see list attached). Outstanding items: Registrar Survey – see additional language added to Annex D of write up to reflect last week’s input (see https://docs.google.com/document/d/1cV5ExSZD6G-owksGmMEmig0OXVdGcAUU/edit [docs.google.com] Language added to reflect current accuracy practices, and survey to ask questions about what registrars might be doing beyond the minimum requirements. Background language on how the questions originated and intent were also added. Discussion of Google forms vs Click Tools for distribution of the survey, depending on the group’s needs. Pros and cons of different tools is to be further considered during the implementation phase. GAC members to provide additional context as to what “reliability of data” means in reference to their registrar stress testing proposal (proposal 5). The group held a discussion on the differences between reliability and accuracy. Stephanie Perrin (NCSG): noted that accurate and reliable mean different things. Reliable implies functionality and that something continues to work. Accurate means that someone is contactable. Sarah Wyld (RrSG): noted that a non-response from a registrant in regards to an inquiry in no way indicates that the data is no longer accurate. Registrars have processes in place for verifying accuracy. Alan Greenberg (ALAC): noted that responses from Compliance, even if a registrant receives an email, they are not obligated to reply. Registrars do not have an obligation to follow-up. Sarah noted in the chat that the RAA has a policy on “How, and to Whom, the WDRP Notice May Be Presented: “the WDRP Notice can be presented via web, fax, postal mail, e-mail, or other appropriate means. It can be presented in one or more languages, including at least the language of the registration agreement. The Notice may be presented to the registrant either directly or through the administrative contact for each registration.” The admin contact is not necessarily the same as the account holder. Further, the admin contact is going away, and notice will be sent to the WDRP owner. Sarah Wyld (RrSG): reliable means that it remains consistent across time, and we've agreed that there are requirements to maintain the accuracy of data in an ongoing manner. A registrar has an obligation if they know data is inaccurate. The group discussed responsibilities regarding a controller and processor arrangement. Scott Austin (IPC): cited 3.3.4 of the RAA. WHOIS service must remain functional overtime. The chair encouraged the GAC representatives to relay this discussion back to the GAC team and report back to the group should further discussion be necessary. Proponents of “stress testing” (ALAC, GAC, IPC, etc.) to provide further information into the dedicated template [docs.google.com] beginning on p. 20. The additional details and context will be reviewed by the team to determine whether the proposal should be included in the write up. The scoping team reviewed the additional information that was provided by the IPC regarding this proposal in the google doc. Providing false data and saying that is true is problematic. Alan Greenberg (ALAC): the purpose of stress testing the system is in hopes to make it better. How do you confirm consent, or get around the need to confirm consent in the stress test? Mystery shopping would ensure the test is fully neutral. Chris Lewis Evans (GAC): shared ideas on how to set up the test like an audit, such as notify registrars and identify a window of time of when the test would happen. Alan Greenberg (ALAC): Random verification to ensure that accuracy is being followed. Alan Woods (RySG): It does appear to be a test of compliance, which is an audit. Stephanie Perrin (NCSG): A key element of this discussion is ICANN's security and compliance responsibilities, and the extent to which they are entitled to use data (both real and imaginary) to ensure Contracted Party (CP) compliance. ICANN is not like a corporation doing its own stress testing (such as a bank or an insurance company). It is, in this respect, acting as a public body performing a regulatory compliance role. Steve Crocker (SSAC): If ICANN cannot do the testing itself, it can simply impose a requirement that each registrar contract with a suitable organization to have it done. Stephanie Perrin (NCSG): As we discuss stress testing, ICANN appears to be carving itself in a limited role as a data controller, as a stand-in for a regulator. This is a function that might be managed by a government in other circumstances (forged under the ITU). Strict limits as to what ICANN do in its current role. This brings us back to conducting an audit. Benefit is to third parties seeking data that is no longer available in the WHOIS replacement. Confirm next steps Chair confirmed no meetings until the 11th. Over the next two weeks, the group to continue discussions via the mailing list: See if consensus can be reached about what has been proposed by ALAC and the IPC, which is a type of enhanced audit functionality that could be used. If the parties wanted to come together, there would be a way to pull that off. By the 11th, if there is consensus, the team could make changes to assignments 1 and 2. If no consensus, groups could submit their concerns/objections in their statements, which will be included in the Annex. The staff support team pointed out that the scoping team had previously considered recommending a registrar audit, but this did not include the concept of stress testing. For a variety of reasons such as the possible timeframe for conducting an audit as well as the inability to conduct an audit on aspects that would require access registration data until there is clarity from the EDBP, the Scoping Team did not recommend moving forward with the audit at that point. Seeing the renewed interest in this approach, the staff support team suggested providing some draft language to the group on a potential recommendation in relation to a registrar audit, which would highlight that further conversation would be needed to determine the if/how/why/what of a registrar audit. If consensus is achieved, the write-up could be included in the final draft. Otherwise, individual community statements to be added to the annex could further detail the proposal. Marc Anderson (RySG): discussed why an audit wasn’t pursued in the first place, it might have had to do with timing and needing over six months to receive the results. Need to go back and review the conversations. ICANN org would have potential GDPR concerns and need approval from the EDPB about accessing registrant data to conduct the audit. ICANN org said given these concerns, it would not include registrant data. The NCSG was interested in exploring the concept of data trusts, to examine oversight/audit capability in an MS environment. ICANN needs to have some kind of oversight over itself, as life gets more complex in the info society. Should ICANN sample domain names from the DAAR reporting? Concern that this might be potentially biased. Hence the idea for ICANN or a third-party vendor, to inject third party registrations and then do the testing. 3. Finalize write up for assignments #1 and #2 for delivery to GNSO Council – see https://docs.google.com/document/d/1cV5ExSZD6G-owksGmMEmig0OXVdGcAUU/edit [docs.google.com] 1. Any outstanding items? 2. Confirm deadline for final review. 3. Confirm next steps. Recommendation for ICANN org to draft language in bracketed text between now and the 11th Aug. Between now and the 11th, to continue discussions with the aim to achieve consensus. If groups want to append statements to the write up for assignments #1 and #2, these need to be submitted by Monday, 8 August 23:59 UTC. Need to show the GNSO Council that assignments 1 and 2 have been completed. Staff will flag on the mailing list when language has been inserted (in the next few days) so members can begin reviewing. If there are questions, please contact Steve Crocker to provide feedback on his proposal. 4. Confirm action items & next meeting (TBC) Next meeting is on Thursday, 11th August.

3 3

Notes and action items - RDA Scoping Team Meeting #36 - 11 August 2022
by Chantelle Doerksen Aug. 15, 2022

Aug. 15, 2022

Dear RDA Scoping Team Members, Please find below the notes and action items from the recent call held on Thursday, 11 August 2022. Best, Marika, Berry, and Chantelle ----- Action Items Michael to send an email with further guidance on next steps and timing to the list. Staff will relay to GNSO Council Leadership that the write up for assignments #1 and #2 will not be ready in time for review and consideration during the Council’s August meeting as originally planned. (COMPLETED) Staff support team to accept all minor edits in the write up. Recommendation #2 will be updated by removing “stress” and addition of footnote as suggested by ICANN org, in addition to edits made during the call in the google doc. Alternative recommendation #2 language will be removed. Notes Welcome & Chair Updates · Mason Cole replaced Susan Kawaguchi as the Business Constituency’s (BC) representative to the team. Review of items flagged for consideration (see https://docs.google.com/document/d/1cV5ExSZD6G-owksGmMEmig0OXVdGcAUU/edit [docs.google.com] )– Scoping team to consider: Recommendation #2 – edits proposed by RrSG and ICANN org · The chair referenced options outlined in his email for moving the draft report forward. · The Intellectual Property Constituency (IPC) would prefer to use another word rather than audit. · Alan Greenberg (ALAC): Text should be modified to note that the analysis should not be in violation of registrar agreements. Group has been discussing the submission of registrations, with potentially false data, to see whether the registrar processes will notice it or not. · Sarah Wyld (RrSG): The gap analysis proposal F is not the same as deep dive Proposal F. It is not clear how the suggestion of doing test registrations is different from Proposals B and C in our gap analysis, which were proposals to do a third party assessment. o The original recommendation was in order for ICANN org to do a registrar audit, we need to think about that separately from the idea of hiring a third party to do testing, because those are two different things. · Agreement to remove the language referencing “stress” testing, as that implies something different than what the group proposed. The use of the word testing would be accepted. We cannot bring in a third party to do stuff we aren’t going to do ourselves (e.g., data processor delegation). · Fictitious data is not permissible under the Registration Agreement. If we grant exemptions we're back to the problem from the last meeting of the testing not being secret anymore. · ICANN staff agreed to translate the conversation from the previous meeting into a recommendation in the report, which is what the proposed language represents. Sarah Wyld, Brian Gutterman, and Alan Greenberg provided input as well as the IPC. · Stephanie Perrin (NCSG): Checks by ICANN org to ensure that things are being done correctly is a little different than an audit. I thought it was confirmed that we couldn’t use false data. · Owen Smigelski (RrSG): RDDS Specification Section 2 of RAA is about Service Level Agreements (SLAs). The RAA amendment is actually currently under way, but narrowly limited to replacing WHOIS with RDAP. There is no possibility to add anything else, including new language to address feasibility to verify compliance by using false registration data. o Some suggested that further exploration might be warranted, while others felt that at this stage this would not be necessary. · Absent any guidance from the European Data Protection Board (EDPB), every registrar will conduct the balancing test individually. The answer is not clear without guidance from the EDPB. Alternative recommendation #2 – proposed by the IPC · IPC believes testing is in the community interest. There needs to be an agreement on some sort of testing that is planned, coordinated, and cooperative. · The NCSG believes ICANN org would have to evaluate its risk in each jurisdiction, which might be a non-starter for legal services. · IPC is happy to withdraw its Alternative 2 language and provide a reasonable edit to Rec 2 that covers concerns related to testing. · Agreement to explore what type of testing would be possible within the current bounds of the RA and RAA. · ICANN org statement to be added as a footnote: “For the record, ICANN Compliance will not submit, directly or through a third party, deliberately false registration data to registrars either as part of an audit or any other enforcement measure.” · Alan Greenberg (ALAC): This is ICANN org’s current interpretation of the RAA. This might be changed and interpreted differently in the future. Alternative recommendation #3 – proposed by the IPC New recommendation #4 – proposed by the IPC · IPC proposed alternative text that all work be suspended until ICANN and contracting parties agree to a Data Processing Agreement that can be shared publicly. · The EU GAC rep at ICANN 74 did indicate in the GAC BOARD meeting that they would respond. Did indicate that the EC would be responding to ICANN’s request. · The staff support team pointed out that the reference to “pausing” in the original recommendation is specific to the consideration of proposals that require access to registration data. e. Confirm next steps · The chair agreed that another call would be needed. He agreed to send out further instructions via email in relation to next steps and timing. Finalize write up for assignments #1 and #2 for delivery to GNSO Council: Confirm timing & next steps Possible meeting at ICANN75 Confirm action items Michael to send an email with further guidance on next steps and timing to the list. Staff will relay to GNSO Council Leadership that the write up for assignments #1 and #2 will not be ready in time for review and consideration during the Council’s August meeting as originally planned. (COMPLETED) Staff support team to accept all minor edits in the write up. Recommendation #2 will be updated by removing “stress” and addition of footnote as suggested by ICANN org, in addition to edits made during the call in the google doc. Alternative recommendation #2 language will be removed.

1 0

Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 18 August 2022 at 14:00 UTC
by Terri Agnew Aug. 15, 2022

Aug. 15, 2022

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 18 August 2022 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/94504686990?pwd=MWc2eXZE…> Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd <https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, alternates and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests 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…> * Visit the Wiki agenda page: https://community.icann.org/x/uYKLD * Check your time zone: https://tinyurl.com/5xcmczrj ONLY for Members and Alternates * Please join via the above Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and so it is captured in the recording. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form <https://urldefense.com/v3/__https:/forms.gle/GZqMAi4kKDaVP5o66__;!!PtGJab4!…> to communicate who the alternate is replacing and for which period. This information will be publicly posted so that the Team is aware at any time who is active. Alternate Assignment –wiki page<https://community.icann.org/x/-wC7Cg>. 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

1 0

Registration Data Accuracy Scoping Team meeting
by ICANN Policy Calendar Aug. 15, 2022

Aug. 15, 2022

Meeting: Registration Data Accuracy Scoping Team meeting Date/time: Thursday, 18 August 2022 at 14:00 UTC for 90 minutes Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/94504686990?pwd=MWc2eXZE…> Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd <https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, alternates and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests 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…> * Visit the Wiki agenda page: https://community.icann.org/x/uYKLD * Check your time zone: https://tinyurl.com/5xcmczrj ONLY for Members and Alternates * Please join via the above Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and so it is captured in the recording. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form <https://urldefense.com/v3/__https:/forms.gle/GZqMAi4kKDaVP5o66__;!!PtGJab4!…> to communicate who the alternate is replacing and for which period. This information will be publicly posted so that the Team is aware at any time who is active. Alternate Assignment –wiki page<https://community.icann.org/x/-wC7Cg>. 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

1 0

Post call | Registration Data Accuracy Scoping Team | Thursday, 11 August 2022
by Terri Agnew Aug. 11, 2022

Aug. 11, 2022

Dear all, All recordings for the Registration Data Accuracy Scoping Team held on Thursday, 11 August 2022 can be found on the agenda wiki page <https://community.icann.org/x/KgBpD> (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 and chat archive) * Audio recording * Zoom recording (including audio, visual, rough transcript and chat) * Transcript For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-accuracy-st/> and the main wiki page<https://community.icann.org/x/hQIuCg>. Thank you! Kind Regards, Terri

1 0

**Starting in 15 minutes | Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 11 August 2022 at 14:00 UTC
by Terri Agnew Aug. 11, 2022

Aug. 11, 2022

**Starting in 15 minutes Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 11 August 2022 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/94504686990?pwd=MWc2eXZE…> Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd <https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, alternates and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests 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…> * Visit the Wiki agenda page: https://community.icann.org/x/KgBpD * Check your time zone: https://tinyurl.com/n5d4vwn7 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/n5d4vwn7__;!!PtGJab4!6GXp7cy…> ONLY for Members and Alternates * Please join via the above Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and so it is captured in the recording. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form <https://urldefense.com/v3/__https:/forms.gle/GZqMAi4kKDaVP5o66__;!!PtGJab4!…> to communicate who the alternate is replacing and for which period. This information will be publicly posted so that the Team is aware at any time who is active. Alternate Assignment –wiki page<https://community.icann.org/x/-wC7Cg>. 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

1 0

Re: [GNSO-Accuracy-ST] Thursday Game Plan
by Marika Konings Aug. 10, 2022

Aug. 10, 2022

Hello All, Brian G (Org liaison) is out this week, but I wanted to flag that ICANN org will need more time to consult internally on these new proposals. Given their very recent introduction there was not adequate time for consultation before the 11 Aug call for org to provide feedback to the team. If the 11 Aug discussion results in a decision to include these proposals (or some adaptation of these proposals) into the team's recommendations, ICANN org will provide its feedback as soon as possible after the call. Best regards, Marika From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces(a)icann.org> on behalf of "michael palage.com" <michael(a)palage.com> Date: Wednesday, 10 August 2022 at 15:05 To: "gnso-accuracy-st(a)icann.org" <gnso-accuracy-st(a)icann.org> Subject: [GNSO-Accuracy-ST] Thursday Game Plan Hello All, As we near the end to the first part of our journey I would like to set expectations for tomorrow’s call. In an ideal world, tomorrow we are able to reach consensus on the comments submitted by the IPC and we conclude our work and our report is sent to the GNSO Council by Monday. (Option A). However, given the last minute submission of the IPC comments, this may not be possible as some stakeholder groups may need more time for internal consultation. Now depending upon the exchange during tomorrow there are two additional options as I currently see it. The first is that there is strong push back from a significant portion of the group suggesting that there is little to no likelihood of any consensus. In this case, I am inclined (unless there is consensus within the group otherwise) to declare an impasse. In this situation, the original text of the report would be finalized and I would ask any member/stakeholder groups to prepare their minority/opposition statements that would be included as an annex. We would need these statements submitted by close of business Monday August 15th to meet existing GNSO Council timelines. (Option B) If I declare an impasse in our work (e.g. there is no consensus within the group against this determination) but there is push back to the Monday August 15th timeline, I will extend the delivery of our final report to the GNSO Council. This delay will likely have the knock on effect of this group not meeting at ICANN75. Notwithstanding any delay needed for the submission of these minority/opposition statements, it is my intention to have a final report sent to the Council by the end of the month. (Option C). Hopefully this provides a clear roadmap to tomorrow’s call. Best regards, Michael

1 0

REMINDER | Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 11 August 2022 at 14:00 UTC
by Devan Reed Aug. 10, 2022

Aug. 10, 2022

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 11 August 2022 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/94504686990?pwd=MWc2eXZE…> Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd <https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, alternates and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests 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…> * Visit the Wiki agenda page: https://community.icann.org/x/KgBpD * Check your time zone: https://tinyurl.com/n5d4vwn7 <https://urldefense.com/v3/__https:/tinyurl.com/n5d4vwn7__;!!PtGJab4!93HsNXa…> ONLY for Members and Alternates * Please join via the above Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and so it is captured in the recording. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form <https://urldefense.com/v3/__https:/forms.gle/GZqMAi4kKDaVP5o66__;!!PtGJab4!…> to communicate who the alternate is replacing and for which period. This information will be publicly posted so that the Team is aware at any time who is active. Alternate Assignment –wiki page<https://community.icann.org/x/-wC7Cg>. 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

2 1