May 2022 - GNSO-Accuracy-ST

Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 19 May 2022 at 14:00 UTC
by Terri Agnew May 12, 2022

May 12, 2022

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 19 May 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/Tg51Cw * Check your time zone: https://tinyurl.com/bdfzehsp ONLY for Members and Alternates * Please join via the above Main Zoom 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

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

May 12, 2022

**Starting in 15 minutes Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 12 May 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/TA51Cw * Check your time zone: https://tinyurl.com/394dpksj [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/394dpksj__;!!PtGJab4!pke5IiL…> ONLY for Members and Alternates * Please join via the above Main Zoom 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

3 2

Re: [GNSO-Accuracy-ST] Proposed Agenda - Registration Data AccuracyScoping Team meeting #29 on Thursday 12 May at 14.00 UTC
by Marika Konings May 11, 2022

May 11, 2022

Thank you, Sarah. In response to your questions, from a staff support team perspective: * Yes – following the review of the gap analysis proposals we’ll either integrate the write up for that part in the google doc or share it as a standalone document so that the Scoping Team can review and make sure it aligns with the team’s discussion. * In relation to your second question, when you refer to ‘gap analysis method selection’ are you referring to the ‘gap analysis proposals’? If that is what you are referring to, we would expect that the Scoping Team would make recommendations to the Council concerning which proposals it would suggest proceeding with, if any. This is also in line with assignment #2 (“The Scoping Team is expected to provide recommendations for how accuracy levels can be determined and measured, including, but not limited to, whether the WHOIS ARS needs a revamp to make it fit for purpose or whether there are other ways in which accuracy levels can/should be measured.") The Council will then need to consider these recommendations, as well as potential resources that would need to be requested to carry out these recommendations and decide how to proceed. See also the related action item below: “RDA Scoping Team to opine, particularly, on the proposals that do not require access to personal data; specifically, could the proposals that do not require personal data move forward, or is there another way that meaningful progress can be made while EDPB outreach is ongoing?” Best regards, Marika From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces(a)icann.org> on behalf of Sarah Wyld <swyld(a)tucows.com> Date: Wednesday, 11 May 2022 at 15:55 To: "gnso-accuracy-st(a)icann.org" <gnso-accuracy-st(a)icann.org> Subject: Re: [GNSO-Accuracy-ST] Proposed Agenda - Registration Data AccuracyScoping Team meeting #29 on Thursday 12 May at 14.00 UTC Hello Scoping Team, The CPH reps have now input our comments into the Report for Assignments 1 & 2. We note that there remain placeholders for both the EDPB input and also the gap analysis brainstorming which resulted in several options for how to assess whether current accuracy requirements are achieved. Will the Scoping Team be able to review an updated version of the report after the yellow-highlighted sections are updated? Finally, we want to confirm if our understanding that the gap analysis method selection and completion will be conducted by the GNSO Council is correct. If not, how and by whom will that decision be made and work be done? Thanks, -- Sarah Wyld, CIPP/E Policy & Privacy Manager Pronouns: she/they swyld(a)tucows.com<mailto:swyld@tucows.com> [cid:image001.png@01D86554.5DB71F10] From: Marika Konings<mailto:marika.konings@icann.org> Sent: May 11, 2022 3:01 AM To: gnso-accuracy-st(a)icann.org<mailto:gnso-accuracy-st@icann.org> Subject: [GNSO-Accuracy-ST] Proposed Agenda - Registration Data AccuracyScoping Team meeting #29 on Thursday 12 May at 14.00 UTC Dear All, Please find below the proposed agenda for the next Registration Data Accuracy Scoping Team meeting which is scheduled for Thursday 12 May at 14.00 UTC. As a reminder: 1. RDA Scoping Team Members to review the Write-Up for Assignments 1 and 2 in its entirety and add proposed edits (using the comment function only) no later than 14:00 UTC on Wednesday, 11 May.https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/ed… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1sScP8MwgDCg4…> 2. RDA Scoping Team to opine, particularly, on the proposals that do not require access to personal data; specifically, could the proposals that do not require personal data move forward, or is there another way that meaningful progress can be made while EDPB outreach is ongoing? https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1sScP8MwgDCg4…>) 3. RDA Scoping Team to review responses from ICANN Compliance and determine if any follow-up questions are needed: https://mm.icann.org/pipermail/gnso-accuracy-st/2022-April/000398.html. Best regards, Caitlin, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #29 Thursday 12 May at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * Project Change Request submitted to the GNSO Council (see https://mm.icann.org/pipermail/council/2022-May/025662.html) * ICANN74 session scheduled for Tuesday 14 June from 11.15 – 12.30 UTC (13.15 – 14.30 local time) 2. Gap Analysis Data Collection Proposals that do not involve access to registration data (30 minutes) (see https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1sScP8MwgDCg4…>) a. Proposal D - Registrar Audit * Opportunity to discuss further with ICANN Compliance * Proposal A - Registrar Survey * Proposal E – Review of Accuracy Complaints d. Confirm next steps 3. Scenarios for EDPB * See update from ICANN org (https://mm.icann.org/pipermail/gnso-accuracy-st/2022-May/000444.html) * Scoping Team feedback by 23 May * Confirm next steps 1. Write up for assignments #1 & #2 (see https://docs.google.com/document/d/13sP-2z7rusEYrDyntrgm-tcIavPMJndU/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/13sP-2z7rusEY…>) (15 minutes) * Review input received * Consider possible recommendations * Confirm next steps 1. ICANN org responses to recent set of questions (see https://mm.icann.org/pipermail/gnso-accuracy-st/2022-April/000398.html) (If follow up questions are identified prior to the meeting) * Reactions / follow up questions * Confirm next steps 1. Confirm action items & next meeting (Thursday 19 May at 14.00 UTC)

1 0

Proposed Agenda - Registration Data Accuracy Scoping Team meeting #29 on Thursday 12 May at 14.00 UTC
by Marika Konings May 11, 2022

May 11, 2022

Dear All, Please find below the proposed agenda for the next Registration Data Accuracy Scoping Team meeting which is scheduled for Thursday 12 May at 14.00 UTC. As a reminder: 1. RDA Scoping Team Members to review the Write-Up for Assignments 1 and 2 in its entirety and add proposed edits (using the comment function only) no later than 14:00 UTC on Wednesday, 11 May.https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/ed… 2. RDA Scoping Team to opine, particularly, on the proposals that do not require access to personal data; specifically, could the proposals that do not require personal data move forward, or is there another way that meaningful progress can be made while EDPB outreach is ongoing? https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit) 3. RDA Scoping Team to review responses from ICANN Compliance and determine if any follow-up questions are needed: https://mm.icann.org/pipermail/gnso-accuracy-st/2022-April/000398.html. Best regards, Caitlin, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #29 Thursday 12 May at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * Project Change Request submitted to the GNSO Council (see https://mm.icann.org/pipermail/council/2022-May/025662.html) * ICANN74 session scheduled for Tuesday 14 June from 11.15 – 12.30 UTC (13.15 – 14.30 local time) 2. Gap Analysis Data Collection Proposals that do not involve access to registration data (30 minutes) (see https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit) a. Proposal D - Registrar Audit * Opportunity to discuss further with ICANN Compliance * Proposal A - Registrar Survey * Proposal E – Review of Accuracy Complaints d. Confirm next steps 3. Scenarios for EDPB * See update from ICANN org (https://mm.icann.org/pipermail/gnso-accuracy-st/2022-May/000444.html) * Scoping Team feedback by 23 May * Confirm next steps 1. Write up for assignments #1 & #2 (see https://docs.google.com/document/d/13sP-2z7rusEYrDyntrgm-tcIavPMJndU/edit) (15 minutes) * Review input received * Consider possible recommendations * Confirm next steps 1. ICANN org responses to recent set of questions (see https://mm.icann.org/pipermail/gnso-accuracy-st/2022-April/000398.html) (If follow up questions are identified prior to the meeting) * Reactions / follow up questions * Confirm next steps 1. Confirm action items & next meeting (Thursday 19 May at 14.00 UTC)

2 2

**REMINDER** Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 12 May 2022 at 14:00 UTC
by Julie Bisland May 11, 2022

May 11, 2022

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 12 May 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/TA51Cw * Check your time zone: https://tinyurl.com/394dpksj [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/394dpksj__;!!PtGJab4!pke5IiL…> ONLY for Members and Alternates * Please join via the above Main Zoom 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] Proposed Agenda - Registration Data Accuracy Scoping Team meeting #29 on Thursday 12 May at 14.00 UTC
by Marika Konings May 11, 2022

May 11, 2022

Reminder, for those reviewing the write up, please use the comment function instead of editing the document directly as that will make it easier for the team to consider the proposed changes before these are applied. Thank you, Caitlin, Berry and Marika From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces(a)icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Wednesday, 11 May 2022 at 09:01 To: "gnso-accuracy-st(a)icann.org" <gnso-accuracy-st(a)icann.org> Subject: [GNSO-Accuracy-ST] Proposed Agenda - Registration Data Accuracy Scoping Team meeting #29 on Thursday 12 May at 14.00 UTC Dear All, Please find below the proposed agenda for the next Registration Data Accuracy Scoping Team meeting which is scheduled for Thursday 12 May at 14.00 UTC. As a reminder: 1. RDA Scoping Team Members to review the Write-Up for Assignments 1 and 2 in its entirety and add proposed edits (using the comment function only) no later than 14:00 UTC on Wednesday, 11 May.https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/ed… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1sScP8MwgDCg4…> 2. RDA Scoping Team to opine, particularly, on the proposals that do not require access to personal data; specifically, could the proposals that do not require personal data move forward, or is there another way that meaningful progress can be made while EDPB outreach is ongoing? https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1sScP8MwgDCg4…>) 3. RDA Scoping Team to review responses from ICANN Compliance and determine if any follow-up questions are needed: https://mm.icann.org/pipermail/gnso-accuracy-st/2022-April/000398.html. Best regards, Caitlin, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #29 Thursday 12 May at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * Project Change Request submitted to the GNSO Council (see https://mm.icann.org/pipermail/council/2022-May/025662.html) * ICANN74 session scheduled for Tuesday 14 June from 11.15 – 12.30 UTC (13.15 – 14.30 local time) 2. Gap Analysis Data Collection Proposals that do not involve access to registration data (30 minutes) (see https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1sScP8MwgDCg4…>) a. Proposal D - Registrar Audit * Opportunity to discuss further with ICANN Compliance * Proposal A - Registrar Survey * Proposal E – Review of Accuracy Complaints d. Confirm next steps 3. Scenarios for EDPB * See update from ICANN org (https://mm.icann.org/pipermail/gnso-accuracy-st/2022-May/000444.html) * Scoping Team feedback by 23 May * Confirm next steps 1. Write up for assignments #1 & #2 (see https://docs.google.com/document/d/13sP-2z7rusEYrDyntrgm-tcIavPMJndU/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/13sP-2z7rusEY…>) (15 minutes) * Review input received * Consider possible recommendations * Confirm next steps 1. ICANN org responses to recent set of questions (see https://mm.icann.org/pipermail/gnso-accuracy-st/2022-April/000398.html) (If follow up questions are identified prior to the meeting) * Reactions / follow up questions * Confirm next steps 1. Confirm action items & next meeting (Thursday 19 May at 14.00 UTC)

1 0

RDA_ST // 30 Apr 2022 Project Package
by Berry Cobb May 6, 2022

May 6, 2022

Dear Scoping Team, Please find a link below to project package for the RDA_ST (30 Apr 2022). This package is a snap-shot at the close of each month and developed by the leadership team to report on the working group’s activities and status of the project. It is also distributed to the GNSO Council to keep them informed as managers of the project. The package is deposited on the wiki so that we can track access statistics. Link: https://community.icann.org/x/PQ2HCg 1. Page 01 – Summary dashboard 2. Page 02 – Project Sitrep – an extract from the Council’s Project List 3. Page 03 – Group roster 4. Page 04,05 – Activity metrics and attendance 5. Page 06 – Project Plan, Gantt chart 6. Page 07 – Work plan & Action items for the period Key points: * The project Status and Health have been downgraded due to missed target dates and uncertainty when the scoping team can complete its assignments #3 and #4. A PCR will be deliberated at the GNSO Council. Please let us know if you have questions. Thank you. B Berry Cobb Policy Development – Senior Program Manager Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: TBD Phone: +1 202 570 7240 Fax: +1 202 789 0104 Twitter: @berrycobb www.icann.org<https://www.icann.org/>

1 0

Notes and action items: RDA Scoping Team meeting #28 - 5 May 2022
by Caitlin Tubergen May 5, 2022

May 5, 2022

Dear RDA Scoping Team Members, Please find below the notes and action items from today’s meeting. Best regards, Marika, Berry, and Caitlin -- Action Items 1. RDA Scoping Team Members to review the Write-Up for Assignments 1 and 2 in its entirety and add proposed edits (using the comment function only) no later than 14:00 UTC on Wednesday, 11 May. https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit 2. RDA Scoping Team to opine, particularly, on the proposals that do not require access to personal data; specifically, could the proposals that do not require personal data move forward, or is there another way that meaningful progress can be made while EDPB outreach is ongoing? (https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit) 3. RDA Scoping Team to review responses from ICANN Compliance and determine if any follow-up questions are needed: https://mm.icann.org/pipermail/gnso-accuracy-st/2022-April/000398.html. 4. Brian G. to share a progress update on the engagement with the EDPB (currently anticipated in advance of next week's plenary meeting). Becky to share a proposed timeline of when ICANN org expects to pose the question to the EDPB. Registration Data Accuracy Scoping Team – Meeting #28 Thursday 5 May at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * ICANN Compliance team to join meeting on 12 May to discuss Registrar Audit Proposal * ICANN org will provide a more detailed update on the EDPB communication in advance of next week’s call. Colleagues responsible for this work will be asked to attend next week’s call and may attend if available * There may be one tightly-worded question to the EDPB regarding gathering data on the state of accuracy – Becky to share proposed timeline of when this will be shared with the EDPB. 1. Write up for assignments #1 & #2 (see https://docs.google.com/document/d/13sP-2z7rusEYrDyntrgm-tcIavPMJndU/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/13sP-2z7rusEY…>) (15 minutes) * High level overview * Initial reactions * So far, no comments or edits have been provided, with the exception of one typographical edit from Marc A. * Is the team comfortable with the write-up as is? * How should the group deal with proposals that are dependent or informed by the EDPB advice? Could the proposals that do not require reg data move forward, or is there another way that meaningful progress can be made while this outreach is ongoing? * How much additional time is needed to review the write-up? * One more week would be helpful. * With respect to the definition in b2, this doesn’t seem to accurately capture everything discussed within the scoping team. It is missing some mapping back to the assignment. The first conclusion is that there is not an agreed upon definition of data accuracy. Registrars proposed the definition that is in the RAA, and that is considered the current state of accuracy (but not necessarily the final state) – text around that is captured in the document. * There are two distinguishable approaches to accuracy – one is in the contracts, which leads to mechanical questions over whether the data is being collected properly. The other important question is – is this fit for purpose? The answer to that can only properly come from the people who use the data. What is in the contract and procedures is an attempt to codify the procedural aspect of satisfying the contract rather than trying to satisfy the uses. * The importance of accuracy is that you cannot have a single definition. The paragraphs report accurately that we did not come up with a definition. The title should be “lack of working definition” or “impracticality of working definition”. * Agree that changing the title would be helpful here * GAC commits to reviewing the write-up to assignment one in advance of the next call * The group needs to be explicit here that it wasn’t able to locate or find a definition of registration data accuracy; everyone seems to agree on this, but it is not explicitly said and should be. NCSG provided a crisp definition in this working document: The Accuracy Scoping Team confirms that they understand accuracy is generally refer to whether something is true, correct, and free from error, and the accuracy of registration data to refer to the degree of correctness when measured against a specified standard. * One notion the group needs to weigh in on is how to handle the proposals that have been discussed – some are dependent on EDPB feedback and others are not. Does the group believe that this prevents movement on the proposals that do not require access to personal data * The group has no control over how quickly the EDPB will respond (if at all) – is there any estimate as to when that will be provided. Saw another message about if the SSAD lite proceeds, the SubPro may have impacts – the same could be true of this work. Think the group could say – yes, we want to proceed with this, but a priority may need to be assigned. It is not urgent, given the other delays in the community. The group should seriously consider if this needs to be done immediately * Becky is committed to coming back to the group with the timing of the EDPB inquiry. * The best the group may be able to do is document the challenges we see. The answer needs to be considered and documented back to the Council. The Council needs to understand with some of the challenges of measuring accuracy. * The write-up is intended to cover the proposals – as part of that – the group would note that some proposals are dependent on whether access to registration data is possible. The group could consider whether it would like to proceed on the proposals that do not require access to registration data. * Discuss timeline for review and how to deal with placeholders * Confirm next steps * Action: please provide comments on the draft 24 hours in advance of the next meeting. 1. ICANN org responses to recent set of questions (see https://mm.icann.org/pipermail/gnso-accuracy-st/2022-April/000398.html) (15 minutes) * There were additional questions that the group sent to ICANN compliance. Answers have been provided, but the group has been working on other work in the meantime and has not discussed or reviewed the answers. * Please review the answers this week and see if any further questions are needed. * Reactions / follow up questions * Confirm next steps 4. Overview of progress made on Gap Analysis Data Collection Proposals (30 minutes)(see https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1sScP8MwgDCg4…>) a. High level overview * The group focused mainly on the proposals that do not require access to registration data. This was done for the registrar survey proposal, and ICANN org registrar audit. ICANN compliance colleagues will be joining next week’s call to discuss the ICANN audit proposal. * Lastly, the group looked at a deeper dive review of accuracy complaints from ICANN compliance. Owen also provided an analysis over email for the group to review. If the group thinks it would be helpful to review these complaints, who would do this? Is it expected to result in information that will help the group move forward? There is one open question related to the survey that would help the group to opine on. * Support Staff’s hope is that, following the discussion with ICANN compliance next week, the group would have a better understanding of the proposals that do not require access to registration data. * Note: the project has been downgraded as the target will be missed. The close of April project package will be submitted shortly. Because of the downgrades, this will invoke the Project Change Request (PCR) – this will be submitted on 9 May and will be shared with the group soon. This is anticipated to be an agenda item for the next Council meeting. This PCR will be atypical as we do not currently have committed-to dates to plug in. * Michael P. plans to step down as chair after the completion of assignments 1 and 2, and this will be communicated to the Council soon. b. Initial reactions c. Confirm next steps 1. Confirm action items & next meeting (Thursday 12 May at 14.00 UTC)

1 0

Post call / Registration Data Accuracy Scoping Team | Thursday, 05 May 2022
by Julie Bisland May 5, 2022

May 5, 2022

Dear all, All recordings for the Registration Data Accuracy Scoping Team held on Thursday, 05 May 2022 can be found on the agenda wiki page <https://community.icann.org/x/RQ51Cw> (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 chat archive * Zoom recording (including audio, visual, rough transcript) * 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, Julie

1 0

Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 12 May 2022 at 14:00 UTC
by Julie Bisland May 5, 2022

May 5, 2022

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 12 May 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/TA51Cw * Check your time zone: https://tinyurl.com/394dpksj ONLY for Members and Alternates * Please join via the above Main Zoom 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