November 2021 - GNSO-Accuracy-ST

Instructions
by Sarah Wyld Nov. 18, 2021

Nov. 18, 2021

Hello team, In an effort to help make it easier to understand and adhere to our instructions, I’ve put them in chart form: https://docs.google.com/spreadsheets/d/1HoNZP_LfeS3TOG_9VBmgHoawg1QauyR68yg… Perhaps if we fill out column C as we go, we can get through this all effectively as a team! (I’m happy to turn over ownership of this doc to ICANN if that’s desireable!) -- Sarah Wyld, CIPP/E Policy & Privacy Manager Pronouns: she/they swyld(a)tucows.com +1.416 535 0123 Ext. 1392

1 0

Re: [GNSO-Accuracy-ST] Purposes vs Requirements
by Steve Crocker Nov. 18, 2021

Nov. 18, 2021

Sarah, et al, With respect to focusing on just the definition of accuracy, is our focus solely on the accuracy of email and phone numbers, or do we anticipate the PDP will be setting rules for the accuracy of the myriad of other data elements? Further, are we providing a single level of accuracy or choices for different levels of accuracy? If our work is aimed at setting a single standard for accuracy, which I assume will be operational validation, and it's intended to apply only to email and phone numbers, then the path forward is easy. We can converge on the wording that defines operational validation, and the PDP will not have any work to do regarding setting the requirements. The implication, of course, is the PDP will say nothing about the accuracy of the other data elements, and the only purposes that can be supported will have to depend solely on operational validation of email and/or phone numbers. Thanks, Steve On Thu, Nov 18, 2021 at 8:19 AM Sarah Wyld <swyld(a)tucows.com> wrote: > Hello all, > > > > It seems to me that listing the agreed-upon purposes that registration > data is supposed to serve may not be part of our instructions, or if we do > need to do so it would be in service of answering Instruction #3: > > > > “3. Effectiveness: The Scoping Team will, on the basis of its assessment > under 1. and data resulting from 2., undertake an analysis of the accuracy > levels measured to assess whether the contractual data accuracy obligations > are effective at ensuring that Registered Name Holders provide “accurate > and reliable” contact information.” > > > > I could see that we can’t assess if obligations are effective without > having an understanding of what effective means, which could relate to the > purpose for collecting registration data. > > > > That said, I don’t think these purposes are related to the work we need to > do for Instructions #1 and #2, which have us assessing how accuracy is > monitored, considering if there is a definition of accuracy (I think there > is), and providing suggestions for how to measure accuracy. > > > > I think we’ll get through this work the most efficiently if we stick to > the plan and follow the schedule we’ve already agreed on, which means > starting with instructions 1 and 2. > > > > Looking forward to discussing! > > > > Thanks, > > > > > > -- > > *Sarah Wyld*, CIPP/E > > > > Policy & Privacy Manager > > Pronouns: she/they > > > > swyld(a)tucows.com > > +1.416 535 0123 Ext. 1392 > > > > > > *From: *Steve Crocker <steve(a)shinkuro.com> > *Sent: *November 17, 2021 7:59 PM > *To: *Marika Konings <marika.konings(a)icann.org> > *Cc: *gnso-accuracy-st(a)icann.org > *Subject: *[GNSO-Accuracy-ST] Purposes vs Requirements > > > > Folks, > > > > Attached is a short note on purposes, requirements, etc. > > > > In my view, the work for this scoping group is to: > > - List the agreed upon purposes that registration data is supposed to > serve. This is presumably just a matter of copying what's been previously > decided, but I've heard some contradictory views, one of which is there are > no acceptable third party uses of registration data. > - Agree on definitions for the various levels of accuracy validation > that might be applied to individual data elements. > > It will then be up to the PDP WG to set the specific accuracy requirements > for individual data elements. > > > > The natural questions along the way are: > > - whether the requirements are sufficient to meet the intended > purposes, > - whether the actual practices achieve the requirements, and > - whether discrepancies between requirements and practice are actually > detected, and, if so, what remedial actions take place. > > See you all on the call tomorrow. > > > > Thanks, > > > > Steve > > > > >

1 0

**Starting in 15 minutes | Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 18 November 2021 at 14:00 UTC
by Terri Agnew Nov. 18, 2021

Nov. 18, 2021

**Starting in 15 minutes Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 18 November 2021 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09 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 [icann.zoom.us]<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 [gnso.icann.org]<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 [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/3AC7Cg * Check your time zone: https://tinyurl.com/5ba4vsun [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/5ba4vsun__;!!PtGJab4!qI5d9D-…> ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Panelists and Attendees, or Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form [forms.gle]<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

Proposed Agenda - Registration Data Accuracy Scoping Team meeting #6 on Thursday 18 November at 14.00 UTC
by Marika Konings Nov. 18, 2021

Nov. 18, 2021

Dear All, Please find below the proposed agenda of the next Registration Data Accuracy Scoping Team meeting which has been scheduled for Thursday 18 November at 14.00 UTC. Best regards, Caitlin, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #6 Thursday 18 November at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) 1. Follow up questions to ICANN org regarding enforcement and Accuracy Reporting System (45 minutes) * Input received from scoping team to date: https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit * Scoping team input * Confirm deadline for submission of questions 1. Homework reminder: * Future explanation / aspirational definition of accuracy see template - https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit) * Deadline: 2 December 2021 1. Confirm action items & next meeting (Thursday 25 November at 14.00 UTC)

3 3

**REMINDER** Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 18 November 2021 at 14:00 UTC
by Julie Bisland Nov. 17, 2021

Nov. 17, 2021

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 18 November 2021 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09 [icann.zoom.us]<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 [icann.zoom.us]<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 [gnso.icann.org]<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 [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/3AC7Cg * Check your time zone: https://tinyurl.com/5ba4vsun [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/5ba4vsun__;!!PtGJab4!qI5d9D-…> ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Panelists and Attendees, or Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form [forms.gle]<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 #5 - 11 Nov 2021
by Caitlin Tubergen Nov. 12, 2021

Nov. 12, 2021

Dear RDA Scoping Team Members, Please find below the notes and action items from this week’s meeting. The next RDA Scoping Team meeting will be Thursday, 18 November at 14:00 UTC. Thank you. Best regards, Marika, Berry, and Caitlin -- Action Items 1. STILL OPEN: RDA Scoping Team members to populate questions to ICANN org in the dedicated Google Doc<https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit> over the coming weeks with a goal to finalize questions by Friday, 27 November. 2. By Thursday, 2 December, each group to identify their future explanation of Accuracy<https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit>, i.e., what should accuracy requirements look like and how should these be implemented and enforced by ICANN org in a future state? As part of this future explanation of accuracy, you are asked to identify what problem(s) this future explanation is expected to address, as well as provide your insights into how this problem has already been documented or how it can be documented as part of the team’s effort to scope the issue. Registration Data Accuracy Scoping Team – Meeting #5 Thursday 11 November at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * Project plan submitted to the GNSO Council (see https://mm.icann.org/pipermail/council/2021-November/025175.html) * The document reviewed by the Team last week was sent the GNSO Council this week. It will be included in the AOB agenda item at the Council’s upcoming meeting. * The meeting will remain at this time going forward; the only variable is whether the meeting will be 60 minutes or 90 minutes. The goal will be to conclude every meeting after 60 minutes. 1. Working definition of accuracy (10 minutes) From assignment #1: “The Scoping Team shall, with reference to the resources that will be included in the index of relevant resources cited below, consider whether there is an agreed definition of registration data accuracy and, if not, consider what working definitions should be used in the context of the Scoping Team's deliberations. Particular attention should be given to the definition that ICANN Compliance employs for “accuracy” in ICANN’s contracts. Note, this does not preclude any subsequent effort from formalising the definition(s) that should be applied in the context of any existing and/or new accuracy requirements that may be developed”. * Consider further input received on definition (see page 12 - https://docs.google.com/document/d/1k9fvA4gnb13bNbB8O4o72mXMZ8mQnJGC/edit[d…<https://urldefense.com/v3/__https:/docs.google.com/document/d/1k9fvA4gnb13b…>) * * Confirm working definition (current state) * During the last meeting, the group came close to rough consensus on a working definition. * Instead of a working definition, propose to refer to it as a working contractual construct * The assignment of the scoping team is to consider whether there is an agreed upon definition and what working definition to use in the context of the scoping team’s deliberations. Now it seems there is proposal to have a working construct. * Suggest that the team does away with the unvarnished meaning of accuracy. There are three kinds of accuracy: identity, syntactic, and operational. The language that should appear in contracts and policies should include the appropriate labels. It would be helpful to use the type of accuracy and then the discussion will be easier. * Accuracy is a loaded word and it means different things to different people in different contexts. Could live with the word definition – what some members are afraid of is that this definition will be set in stone and many are not OK with the current definition. * The group is starting with an explanation of the current state of affairs. Do members agree that this is an accurate capture of the current definition in existing contracts? If the group does not start with a shared point, it will be messy. Understand there are three types of accuracy defined by others, but that gets into questions 3 and 4. This assignment is – what is the current state, and can the group agree on it. * The words on the paper need to say current and have a disclaimer so that it is clear * There is a different level of checking for phone number and email then for names – it’s important to explain the different levels * Confirming that the group has viewed comments from Melina and Lori – does this belong here or in the aspirational discussion? Melina would like reference to purposes in ICANN Bylaws and purposes in EPDP Phase 1 1. Aspirational definition of accuracy (10 minutes) * Overview of homework assignment (see template - https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUs…>) * Groups are now to work together to come up with their aspirational definition * The idea is that the group now has a current state definition. Many members have spoken about what the definition “should be”, which is why leadership is using the term aspirational. However, most have not provided why the definition should be changed. Groups are now asked to provide what the definition should be and then explain what problem this change is trying to address. Then, is there data that confirms that this problem exists? If there is no data currently, what data is necessary to gather to further understand the perceived problem? * The definition in the RAA only applies for new registrations and to certain fields. * To answer this question, the group should look at the final purposes of the EPDP Phase 1. * The EPDP team did not agree to the definition of accuracy vis-à-vis GDPR. The EPDP team was discussing purposes based on the RAA. This should not be the basis for going forward. * The definition used for accuracy was under dispute throughout the EPDP. The reason we have for accuracy is for contactability which does include third parties. * The work of this group for assignment 1 and 2 is not in scope to be relitigating or reopening the work in EPDP Phase 1, 2, or 2A. If the group identifies a problem, it could identify issues for the Council to reconsider. * Whatever the group is discussing in terms of accuracy must stay within the bounds of what was discussed in the EPDP. * In the third column, the word need has been added – what problems and/or needs is this future definition expected to address * Scoping team input * Aspirational is a loaded term. What is the need that accuracy is trying to fill – what goal is it trying to reach? Does the current definition meet that need? This is not a shopping list of items that we would like accuracy to do. The chart gets to this. * Looking at this as an aspirational definition could lead the group down a rabbit hole. Trying to agree to an aspirational definition could cause a lot of consternation. * Confirm next steps & deadline for input 1. Follow up questions to ICANN org regarding enforcement and Accuracy Reporting System (30 + minutes) * Note additional information added to the index of relevant resources from RDS-WHOIS2 RT, including responses to questions * Input received from scoping team to date: https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit[d…<https://urldefense.com/v3/__https:/docs.google.com/document/d/1arlKdQkbRkE1…> * Scoping team input * The document that staff prepared for Council is very thorough – referring specifically to the a26 Feb 2021 letter from Swinehart to Fouquart. This dovetails into the group’s first task nicely. After reading this document, did not come away with what definition ICANN uses. Perhaps this would be good fodder for a follow-up question with ICANN org. What does ICANN Compliance consider the current definition of accuracy and does that comply with the definition proposed by registrars? * Support the above * Important for the group to discuss these questions. * There is a Compliance blog post about enforcement – please read this document and determine if additional questions are necessary. Also review the question and additional information Sarah Wyld put into the document. * This work needs to take place intersessionally between the working calls; the calls cannot be used for the drafting of questions in order for the group to make progress. * Confirm deadline for submission of questions 1. Confirm action items & next meeting (Thursday 18 November at 14.00 UTC)

1 0

Registration Data Accuracy Scoping Team | Thursday, 11 November 2021
by Terri Agnew Nov. 11, 2021

Nov. 11, 2021

Dear all, All recordings for the Registration Data Accuracy Scoping Team held on Thursday, 11 November 2021 can be found on the agenda wiki page <https://community.icann.org/x/1AC7Cg> (attendance included) and the GNSO Master Calendar [gnso.icann.org]<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, Terri

1 0

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

Nov. 11, 2021

**Starting in 15 minutes Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 11 November 2021 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09 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 [icann.zoom.us]<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 [gnso.icann.org]<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 [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/1AC7Cg * Check your time zone: https://tinyurl.com/znz8kmf4 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/znz8kmf4__;!!PtGJab4!psV4Gwm…> ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Panelists and Attendees, or Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form [forms.gle]<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

Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 18 November 2021 at 14:00 UTC
by Terri Agnew Nov. 11, 2021

Nov. 11, 2021

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 18 November 2021 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09 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 [icann.zoom.us]<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 [gnso.icann.org]<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 [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/3AC7Cg * Check your time zone: https://tinyurl.com/5ba4vsun ONLY for Members and Alternates * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Panelists and Attendees, or Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form [forms.gle]<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

Proposed Agenda - Accuracy Scoping Team meeting #5 - Thursday 11 November at 14.00 UTC
by Marika Konings Nov. 10, 2021

Nov. 10, 2021

Dear All, Please find below the proposed agenda for the next Registration Data Accuracy Scoping Team which is scheduled for Thursday 11 November at 14.00 UTC. As a reminder: 1. RDA Scoping Team members to review the most recent working definition for accuracy (p. 12 of the Assignment 1 background briefing doc [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1k9fvA4gnb13b…>) and provide proposed edits or alternate definitions by COB Wednesday, 10 November. Once the Team agrees to the baseline working definition, groups can begin working on their proposed “aspirational” or “desired future state” definitions. 2. RDA Scoping Team members to populate questions to ICANN org in the dedicated Google Doc [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1arlKdQkbRkE1…> over the coming weeks with a goal to finalize questions by Friday, 27 November. Best regards, Caitlin, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #5 Thursday 11 November at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * Project plan submitted to the GNSO Council (see https://mm.icann.org/pipermail/council/2021-November/025175.html) 1. Working definition of accuracy (10 minutes) From assignment #1: “The Scoping Team shall, with reference to the resources that will be included in the index of relevant resources cited below, consider whether there is an agreed definition of registration data accuracy and, if not, consider what working definitions should be used in the context of the Scoping Team's deliberations. Particular attention should be given to the definition that ICANN Compliance employs for “accuracy” in ICANN’s contracts. Note, this does not preclude any subsequent effort from formalising the definition(s) that should be applied in the context of any existing and/or new accuracy requirements that may be developed”. * Consider further input received on definition (see page 12 - https://docs.google.com/document/d/1k9fvA4gnb13bNbB8O4o72mXMZ8mQnJGC/edit) * Confirm working definition (current state) 1. Aspirational definition of accuracy (10 minutes) * Overview of homework assignment (see template - https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit) * Scoping team input * Confirm next steps & deadline for input 1. Follow up questions to ICANN org regarding enforcement and Accuracy Reporting System (30 + minutes) * Note additional information added to the index of relevant resources from RDS-WHOIS2 RT, including responses to questions * Input received from scoping team to date: https://docs.google.com/document/d/1arlKdQkbRkE1LuurmDdd-PZP184_AdFm/edit * Scoping team input * Confirm deadline for submission of questions 1. Confirm action items & next meeting (Thursday 18 November at 14.00 UTC)

2 1