- GNSO-Accuracy-ST - lists.icann.org

Notes and action items - RDA Scoping Team Meeting #14 - 20 Jan 2022
by Caitlin Tubergen Jan. 21, 2022

Jan. 21, 2022

Dear RDA Scoping Team, Please find below the notes and action items from yesterday’s meeting below. Best regards, Marika, Berry, and Caitlin -- Action Items 1. RDA Scoping Team to review ICANN org’s recent memo on the Whois Accuracy Reporting System (Whois ARS). Please see email here: https://mm.icann.org/pipermail/gnso-accuracy-st/2022-January/000236.html. 2. Still Outstanding: By Wednesday, 26 January, Scoping Team to consider what is needed and from whom to obtain information identified as necessary to measure whether current goals are met. Additionally, scoping team members to begin identifying specific ways in which measurement can be undertaken. As noted during today’s meeting, Support Staff has begun inputting the responses received from the Gap Analysis here: https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit?p…. Registration Data Accuracy Scoping Team – Meeting #14 Thursday 20 January at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * Vice-chair – review expressions of interest received, if any * To date, no expressions of interest for vice-chair have been received. * Proposal: continue with no vice-chair for now. * Would anyone object to Olga stepping in as a chair on an interim basis in the event Michael is unavailable? * No objections noted. * Upcoming meetings: • GNSO Policy Webinar on 22 February at 14:00 UTC * This webinar will be hosted by ICANN org * There will be an update from Michael regarding the work of this team, for anyone interested in joining • ICANN73 Accuracy Scoping Team meeting scheduled for 7 March at 12:30 – 14:00 (local time) / 16:30 – 18.00 UTC * The standard meeting time will not occur the week of ICANN73 * For the ICANN73 session, please be sure to register for the session 1. ICANN org responses to Scoping Team questions (45 minutes) * Review scoping team follow up questions / comments (see https://community.icann.org/x/mdMGCw) * Brian sent two communications to the Team: (1) response to follow-up questions from last week and (2) a memo from Org colleagues regarding the Whois Accuracy Reporting System (ARS) * With respect to the question regarding the DPA negotiations – following the Board’s adoption of the EPDP Phase 1 recommendations, a group of CPs and ICANN org colleagues have been working on the DPA * Additional Q & As * How does ICANN org square its controller role with lobbying European parliament? Specifically, should a civil society rep be added to these discussions since there are two sides to this argument? * What is the 66% of “other”? * There is a list of options for reporters to use when submitting complaints; however, reporters may have another reason that is not provided. The “other” category is a catch-all. This is a list the reporter picks themselves, and, accordingly, the category should be taken with a grain of salt as not every reporter is as familiar with the system. It may, for example, be a reporter that is trying to purchase a domain name. * Complaints remain confidential until the complaints have reached a breach status. * Compliance does provide metrics on how many complaints are closed, how many result in first notice, etc. * Metrics may not provide specific trends regarding non-compliance with a specific provision; however, there are metrics regarding specific issues like UDRP or WHOIS inaccuracy. However, there are no public numbers regarding issues related to specific contracted parties. * If there are trends related to WHOIS inaccuracy complaints, for example, Compliance may use this as a tool regarding a policy or a region to discuss clarifications on requirements. This could involve engaging in conference calls or regional events. * Is there any thought into outsourcing compliance functions? * There are no recommendations yet – this is a big question – not sure if this is something that should be discussed yet. * This could be a two-part question: compliance and auditing – reorganizing the compliance function may be a separate question * Compliance does not have numbers for legal persons complaining about domain theft – the metrics do not go down to this level * Registrars have cited the existing contractual requirements as the working definition of accuracy * There seems to be confusion as to what is validation and what is verification. Validation is making sure that all fields are filled in and in the correct format, e.g., UPU. Verification requires sending a communication to email/phone. * Registrars validate that fields are accurate * Registrars needed different terminology for different kinds of accuracy checking. ICANN and registrars agreed to check that all fields are in the formats that they have to be in – that the postal address is formatted in the UPU standard. * Validation and verification are definitions – they may be poor choices, but they are the definitions we have right now. We could propose to invert them or change them. Not sure if further elaboration on them is a good use of this group’s time. * After reading the CCT report from 2018, p. 5 notes that Whois Accuracy complaints remain the largest category of complaints to Compliance. Prior to 2018, was this an accurate statement? Is it now true that it is no longer the largest number of complaints? * Do not have the exact number of complaints, but that sounds correct. * Is there a professional opinion on this change? * No – would refer the group review the metrics to examine the facts. * If a domain name is already on clienthold, these would be closed before going to the contracted party. * When did this particular processing decision occur and why? Just because a domain name is inactive, it doesn’t mean accurate information is associated with it. * The WAPS does mention suspension as a potential outcome of investigation - This kind of process existed prior to GDPR and may have existed prior to the 2013 RAA. This may have come down to how a suspension impacts a registrant’s ability for updates to be made to Whois data. * There are two ways to respond to inaccurate complaints: delete the domain name or suspend the domain name. If the domain name is already suspended, what would ICANN ask Compliance to do? * The correction of Whois data is not something that can be enforced; if the registrar does not have the data, it cannot correct it. Inaccurate data allows a quicker road to suspension. * There are reports of suspended domain names that mysteriously become unsuspended with the same information. Understand that Compliance is now auditing this. * There may be reasons to remove a suspension from a domain name – if a registrant comes back and shows evidence, registrars could reactivate the name. In other cases, it may be a problem with how a registrar may implement its suspension. The RAA is clear that the name cannot be un-suspended unless there is a confirmation or updated information. * At the end of the response of Q17, if the registrant has names already registered, reverification may not be required. Do registrars allow the same registration information for multiple domain names? * If I own a domain name, why would I not be allowed to own another domain name? There may be separate accounts for business needs. * If I purchase a domain name and use the same registration data as another account, would that be prohibited? There is no policy requirement from prohibiting this. * Some registrars operate on a wholesale basis, so there could be multiple account holders with the same registrant. Account holders could be third parties that provide services for registrants (like resellers) * If someone provides an email address that has been verified by someone else, and it no longer has to be validated, that is concerning * Concern: bad guys could use an info set already verified to avoid verifying their own information. Does anyone have information that this actually happens? How would a criminal get this information? The registration information is typically redacted. * This does happen. However, the verification happens per registrar. Some criminals planning to engage in abusive activity would use a well-known brand’s email address. There is no clear way to resolve this quickly – the bad guy would get their 15 days of a live domain name. It should be noted why a domain name was suspended. * Should not be concerned with how often this happens if this is a vector for abuse. * Abusers register domain names in the name of companies to show that this is a legitimate site – rarely saw registrants using email addresses of the abused entities since emails get sent to these entities. This is a non-problem. * Hearing concerns that are anecdotal or historical. Disagree with not being concerned with how often this occurs. If it should be more difficult to lift a domain suspension than it currently is – this could adversely affect real domain owners. If it is harder to lift the suspension, this would affect real people and this is something to consider when suggesting solutions – these should be proportional. Please remember to look at facts and solve concrete problems. * With respect to NIS and FIDO requirements regarding authentication, that may get to some of the questions regarding identity theft. 1. Gap Analysis (10 minutes) * Finalize review of input (still missing BC): https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUs…> * Scoping team input * Confirm next steps 1. Measurement of current goals identified (20 minutes) – see page 25 https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUs…> (20 minutes) * Review input received * Confirm next steps 1. Confirm action items & next meeting (Thursday 27 January at 14.00 UTC)

1 0

ICANN Org Memo on the WHOIS Accuracy Reporting System (ARS)
by Brian Gutterman Jan. 20, 2022

Jan. 20, 2022

Dear Michael and members of the Data Accuracy Scoping Team, Kindly find attached a memo from Org on the WHOIS Accuracy Reporting System (ARS) with up-to-date/supplemental information and thinking from the Org on ARS background, issues and potential future studies. This memo was produced by colleagues from the Org Global Domain and Strategy team led by @Karen Lentz<mailto:karen.lentz@icann.org> and @Jared Erwin<mailto:jared.erwin@icann.org> who are included here in cc. We hope this memo is useful in our ongoing discussions around the ARS and other related issues and stand ready to answer follow-up questions and join future discussions on these topics as they arise moving forward. Best, Brian

2 1

Post call | Registration Data Accuracy Scoping Team | Thursday, 20 January 2022
by Terri Agnew Jan. 20, 2022

Jan. 20, 2022

Dear all, All recordings for the Registration Data Accuracy Scoping Team held on Thursday, 20 January 2022 can be found on the agenda wiki page <https://community.icann.org/x/8oD3Cg> (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

Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 27 January 2022 at 14:00 UTC
by Terri Agnew Jan. 20, 2022

Jan. 20, 2022

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 27 January 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 [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/9ID3Cg * Check your time zone: https://tinyurl.com/4h5xsj8t 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 to be captured afterwards. * 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, 20 January 2022 at 14:00 UTC
by Terri Agnew Jan. 20, 2022

Jan. 20, 2022

**starting in 15 minutes Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 20 January 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 [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/8oD3Cg * Check your time zone: https://tinyurl.com/5n728wpu [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/5n728wpu__;!!PtGJab4!vqrDLyl…> 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 to be captured afterwards. * 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

Org Responses to Follow-Up Questions from Scoping Team
by Brian Gutterman Jan. 19, 2022

Jan. 19, 2022

Hi all, Kindly find attached responses (in line in blue) from Org to the follow-up questions (per our internal notes taken of questions asked aloud and in the chat) asked by the Scoping Team during last week’s briefing/overview of the org answers to the initial set of questions<https://community.icann.org/pages/viewpage.action?pageId=184996761>. I’ll also provide a brief overview (together with a colleague joining from the Compliance team) of these follow-up question responses during tomorrow’s team call. We hope the team finds this additional information useful. Best, Brian From: Brian Gutterman <brian.gutterman(a)icann.org> Date: Wednesday, January 12, 2022 at 8:46 AM To: Michael Palage <michael(a)palage.com>, Marika Konings <marika.konings(a)icann.org> Cc: "gnso-accuracy-st(a)icann.org" <gnso-accuracy-st(a)icann.org> Subject: Responses to Finalised list of questions for ICANN org Dear Registration Data Accuracy Scoping Team Colleagues, Please find attached the ICANN org responses to the questions from the team (answers are included in line in blue). We hope these answers are useful and can help move the groups discussions forward. We’ll provide a brief overview of the answers tomorrow, and will also allow everyone digest the information and come back with follow-up questions next week should they arise. Of course, throughout our scoping exercise the org stands ready to work with the team to help in whatever way we can. Very best, Brian From: Marika Konings <marika.konings(a)icann.org> Date: Thursday, December 16, 2021 at 9:34 AM To: Brian Gutterman <brian.gutterman(a)icann.org> Cc: "gnso-accuracy-st(a)icann.org" <gnso-accuracy-st(a)icann.org> Subject: Finalised list of questions for ICANN org Dear Brian, On behalf of Michael Palage, Chair of the Registration Data Accuracy Scoping Team, please find attached the finalised list of questions for ICANN org. Best regards, Caitlin, Berry and Marika

1 0

**REMINDER** Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 20 January 2022 at 14:00 UTC
by Julie Bisland Jan. 19, 2022

Jan. 19, 2022

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 20 January 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 [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/8oD3Cg * Check your time zone: https://tinyurl.com/5n728wpu [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/5n728wpu__;!!PtGJab4!vqrDLyl…> 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 to be captured afterwards. * 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

Proposed Agenda - Registration Data Accuracy Scoping Team meeting #14 on Thursday 20 January at 14.00 UTC
by Marika Konings Jan. 18, 2022

Jan. 18, 2022

Dear All, Please find below the proposed agenda for the next Registration Data Accuracy Scoping Team meeting which has been scheduled for Thursday 20 January at 14.00 UTC. As a reminder, by COB Wednesday 19 January: * Scoping Team Members to review ICANN org responses to questions and provide follow-up questions (if any) in writing to the mailing list. (Support Staff will then add all questions received to the wiki page: https://community.icann.org/pages/viewpage.action?pageId=184996761.) * Scoping Team to consider what is needed and from whom to obtain information identified as necessary to measure whether current goals are met. Additionally, scoping team members to begin identifying specific ways in which measurement can be undertaken. As noted during today’s meeting, Support Staff has begun inputting the responses received from the Gap Analysis here: https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit?p…<https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit?p…> * If a member would like to serve in the capacity of vice-chair, please express your interest. Best regards, Caitlin, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #14 Thursday 20 January at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * Vice-chair – review expressions of interest received, if any * Upcoming meetings: · GNSO Policy Webinar on 22 February at 14:00 UTC · ICANN73 Accuracy Scoping Team meeting scheduled for 7 March at 12:30 – 14:00 (local time) / 16:30 – 18.00 UTC 1. ICANN org responses to Scoping Team questions (45 minutes) * Review scoping team follow up questions / comments (see https://community.icann.org/x/mdMGCw) * Additional Q & As 1. Gap Analysis (10 minutes) * Finalize review of input (still missing BC): https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit * Scoping team input * Confirm next steps 1. Measurement of current goals identified (20 minutes) – see page 25 https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit (20 minutes) * Review input received * Confirm next steps 1. Confirm action items & next meeting (Thursday 27 January at 14.00 UTC)

1 0

Notes and action items - RDA Scoping Team - Meeting #13 - 13 Jan 2022
by Caitlin Tubergen Jan. 13, 2022

Jan. 13, 2022

Dear RDA Scoping Team members, Please find below the notes and action items from today’s call. The next meeting will be Thursday, 20 January at 14:00 UTC. Best regards, Marika, Berry, and Caitlin -- Action Items 1. Scoping Team Members to review ICANN org responses to questions and provide follow-up questions (if any) in writing to the mailing list by COB Wednesday, 19 January. (Support Staff will then add all questions received to the wiki page: https://community.icann.org/pages/viewpage.action?pageId=184996761.) 2. Scoping Team Members to review follow-up questions from today's meeting (as captured in the meeting notes and flag if these questions need to be updated by COB Friday, 14 January. 3. STILL OUTSTANDING: By Wednesday, 19 January, Scoping Team to consider what is needed and from whom to obtain information identified as necessary to measure whether current goals are met. Additionally, scoping team members to begin identifying specific ways in which measurement can be undertaken. As noted during today’s meeting, Support Staff has begun inputting the responses received from the Gap Analysis here: https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit?p… 4. STILL OUTSTANDING: BC colleagues to input feedback into Gap Analysis as soon as possible. Registration Data Accuracy Scoping Team – Meeting #13 Thursday 13 January at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * Vice-chair – volunteers? Proposed deadline for expressions of interest Wednesday 19 January. * This is currently an open item. If a member and would like to serve in the capacity of vice-chair, please express your interest by COB Wednesday, 19 January. 1. ICANN org responses to Scoping Team questions (30 minutes) * High level overview * This is an opportunity to provide a high-level overview of the content of ICANN org’s response to the questions; however, given that these answers were distributed less than 24 hours ago, members are welcome to digest the answers and ask follow-up questions after reading the questions. * The GDPR has limited access to registration data for all parties, including ICANN and the Compliance Team. Accordingly, this limits ICANN’s ability to check the accuracy data. ICANN org is in communication with relevant authorities in Europe re: GDPR and NIS2 legislation. * With respect to compliance staff training, there is a robust training program that includes training on the contract and consensus policies. * ICANN org endeavored to provide tangible examples where possible. For example, question 4 provides example of types of complaints. * Specific data and metrics are all provided. Compliance has a robust dashboard for data points. Recommend going to this link if there is further interest: https://features.icann.org/compliance/dashboard/2021/0121/report. * Compliance reviewed the definition put forward by registrars, based on the RAA and noted it does not employ its own definition of accuracy but relies on what is in the RAA. * With respect to the Q on ARS, ICANN org is working on a more comprehensive memo on ARS. * Scoping team follow up questions / comments * How is the Compliance team trained on GDPR specifically? * Are the metrics from Compliance based on complaints received? (Answer: yes.) Would be interested to know – prior to the GDPR, how did ICANN perform these checks? * What is the status of the DPA negotiation between ICANN org and contracted parties? * Is the ability for ICANN to share any of the training materials possible? (For example, it has been difficult for the group with respect to wordsmithing. If there are documents regarding clarity on these issues, it would be very helpful.) * With respect to Q3, it discusses issues that are out of scope. How would a third party complainant ever file a complaint regarding the accuracy of registrant data behind a P/P service? When is a complaint in scope and when is it out of scope? * With respect to the engagement you are doing on the NIS2…exactly what kind of purpose are you lobbying for? How does it fit with ICANN’s controller role? Who else do you think should be able to avail themselves of that “legitimate purpose” role to check accuracy? Do you envisage outsourcing and how would that work? Who are you engaging with, the EC or the DPAs? * On the answer to Q21, Do not disagree with second and third paragraphs of this response; however, do not believe it belongs in a definition. The operational activities taken to make something accurate is not part of the definition of what is accurate. * On the answer to Q21, the second to last line uses the term “patently inaccurate”. How is “patently inaccurate” determined? For example, the name Mickey is an actual name. There are times where data may look fishy but is, in fact, correct. How does ICANN org make this determination? * Next steps * What is the preferred format for follow-up questions after this call? * Action: Members to submit follow-up questions in writing to the mailing list. Support Staff will then extract all questions into the dedicated wiki page here: https://community.icann.org/pages/viewpage.action?pageId=184996761. 1. Gap Analysis (20 minutes) * Responses to questions raised in relation to GAC input during meeting #11 * Continue review of remaining input (ISPCP, still missing BC): https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit[d…<https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUs…> * BC input is still not finished – endeavor to submit this by COB today * ISPCP input: There do not seem any additional goals with respect to accuracy. * It is problematic to define additional goals beyond the processing purposes defined by the EPDP. However, additional work is required to properly implement the EPDP recommendations, such as international data transfers. * Operationally, the most important aspect is that the data - as provided by the registrant or account holder, is accurately processed by the contracted parties and not altered by technical flaws, human errors or external actors, e.g., in the context of cyber security threats. * The GNSO Council should work on any upcoming issues and potentially launch additional policy work. To the extent that problems arise in the context of the RAA, that would likely be contractual issues that might need to be covered by ICANN compliance. * Being able to register a domain name and allowing start-ups to use digital real estate as quickly as possible is important. Should not conflate this with the debate on authentication. There are rules in the financial sector for determining that a counterpart for a company is who they claim to be. However, the point here is that data processing is as secure as possible. * Concerned with proposal of NIS directive b/c it may contradict the goals of the SSAD. Asking CPs to check and verify data – it is unclear if this is intended for registrars only or registries as well. If data is not immediately verified, do not know if a company will lose its name immediately. NIS2 is a directive and is still has to be legislated into national laws. * Can ISPCP please elaborate on the additional policy work, and what he would see as the documentation that would be required to trigger it? * The question asks who should be working on issues – in answering the question, discussed the places this work can be done. Do not, however, see necessary additional policy work currently. * * Scoping team input * Confirm next steps 1. Measurement of current goals identified (20 minutes) – see page 25https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUs…> (20 minutes) * EPDP Team to consider what is needed and from whom to obtain information identified as necessary to measure whether current goals are met * Now that the team has gone through most of the input (still awaiting BC input), it is time to discuss how to measure whether the objectives stated by groups are being met * In this document, Support Staff created a new table on p. 24, where the responses to Q2 are copied and pasted. There is also a new column where members can start providing more specifics as to what is needed and by whom. For example, registrar can measure the accuracy and should be able to have that information, so how can the group get access to this info? How would this be done? Similarly, other groups provided suggestions about how data could be obtained. * Thus far, no input has been received. * GAC response to questions received from Gap analysis: In relation to Q1 regarding current goals of accuracy, not fully convinced that the current state (as described at the bottom of this document) captures accurately the ‘existing accuracy requirements and enforcement’. We believe that there has to be a more holistic approach when capturing the current state of play and not limit our analysis to the WHOIS Accuracy Program Specification (WAPS). * With respect to comment about being on the same page, GAC agrees, but believes the current state of play is not limited to operational and syntactical accuracy. * Surprised to see this list referenced. The way it is listed of ICANN’s identification of purposes – this list is not the same as the EPDP-identified purposes, and the EPDP-identified purposes are the purposes this group was expected to consider. * In terms of whois.icann.org – action item to check with ICANN org team that owns this page – believe it is more of a historical documentation, but it may not be what this group should use as the authoritative source to build off of. * Which purposes are problematic here? * If the EPDP team agonized over the purposes, why should they be further discussed? * Believe if some believe the additional purposes are no longer valid and some believe they are, these should be further discussed. * The relevance of these purposes is in question. The value for this team with respect to the accuracy question is the data that pertains to the registrant, and this was agonized over by the EPDP. * There is no final order that the EPDP purposes are error or mistake-free. If looking at this list raises an issue where some members believe there is a possibility that the Phase 1 work omitted something, it should be flagged for future work. If there is no gap, the team can move on. * There is a difference between uses and purposes; accordingly, recommend using the EPDP-identified purposes * Confirm next steps 1. Confirm action items & next meeting (Thursday 20 January at 14.00 UTC)

1 0

Post call | Registration Data Accuracy Scoping Team | Thursday, 13 January 2022
by Terri Agnew Jan. 13, 2022

Jan. 13, 2022

Dear all, All recordings for the Registration Data Accuracy Scoping Team held on Thursday, 13 January 2022 can be found on the agenda wiki page <https://community.icann.org/x/8ID3Cg> (attendance included) and the GNSO Master Calendar<https://gnso.icann.org/en/group-activities/calendar>. 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