January 2022 - GNSO-Accuracy-ST

Notes and action items - Registration Data Accuracy Scoping Team meeting #15 - 27 January 2022
by Marika Konings Jan. 27, 2022

Jan. 27, 2022

Dear All, Please find below the notes and action items from today’s Registration Data Accuracy Scoping Team meeting. Best regards, Caitlin, Berry and Marika -- Action Items 1. Leadership team to further consider proposal to pull the hard data out of the gap analysis input received to allow for review and discussion by the Scoping Team during upcoming leadership meeting. 2. RDA Scoping Team to review ICANN org’s recent memo on the Whois Accuracy Reporting System (Whois ARS) and identify any follow up questions. Please see email here: https://mm.icann.org/pipermail/gnso-accuracy-st/2022-January/000236.html. 3. Still Outstanding: By Wednesday, 2 February, 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.(see https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit?p…<https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit?p…>). Notes & Action items Registration Data Accuracy Scoping Team meeting on 27 January 2022 1. Welcome & Chair Updates (5 minutes) * Assignment 1 write up * Staff support team has started working on a write up of assignment #1 and #2, reflecting deliberations to date. * Intent is to have a report on these assignments to the GNSO Council by ICANN73. * Group is close on completing assignment #1 and hopefully progress can be made on assignment #2 in the coming weeks. 1. Gap Analysis (10 minutes) * Finalize review of input: https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit<https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUs…> * Scoping team input * Confirm next steps * BC input was provided since last review of the gap analysis – see https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit?p… Discussion on entry 1. * How is the BC statement a goal of accuracy? Isn’t this information that belongs on a web-site? * Given that this has been a difficult area for discussion, what if there would be a differentiation between those who make the information available and those who do not? If you ask for the information, you are either provided that info or you are not. You can make your decision on whether you want to do business with them based on that response. If that information would be available for people to view (whether information is shared) would that help? If one needs to reach out proactively before making that decision, instead of being able to view that web-site, may not happen. Registrant information is critical to those who protect the internet, even if most registrants may not look for that information. * How could this change under current GDPR guidance? * There is value to having data for research but under GDPR this has become more difficult. Not necessarily related to the accuracy conversation. Availability may not be part of the scope of this effort. * Focus seems to be on access to data not the accuracy of the data. * Per phase 1 report, registrants have the option to publish their data so those looking to build trust and provide a mechanism for people to see who is behind a site they have the ability to do so. * SSL certs may give more sense of comfort of who you are doing business with instead of Whois data. * Although contactability is not the same as accuracy, there is a correlation – if you don’t have accurate data, you are not able to contact someone. * Upcoming ICANN meeting will also talk about compromised vs. malicious registrations – in both those cases the accuracy of the data plays a role, either to be able to warn the registrant or to be able to assess that there may be an issue if the data is inaccurate. * First need to gather evidence that there is an issue with accuracy that justifies policy work. Need to focus on accuracy, not the purposes of Whois. * Need to be able to assess what the status is of accuracy post-GDPR as before that it was the #1 complaint received by ICANN Compliance. * Documenting and fact finding sooner rather than later is key. * We cannot see accuracy as distant from purposes – need to look at it holistically. If you have context of contactability, you need to assess whether the data is accurate to serve that purpose. Instructions also note that EPDP purposes can be considered. * GDPR should not be blamed for inaccessibility of data – it puts into place safeguards for data processing, it does not prohibit processing of personal data. It only relates to natural persons. * Lack of access to data does not prove that data is more accurate, still complaints. * If inaccurate data is hindering contactability, that is a problem and in scope of group’s work, but this should not be seen as the same as access to the data. Being able to contact the registrant, either via a web form or email is already required and revisiting that requirement is out of scope, but if a registrant is not contactable as a result of inaccurate data that is within scope. In addition, there is also a requirement to have an abuse contact. * Current use of web-forms does not guarantee delivery, is dependent on registrar to deliver. This is an access / disclosure issue, not an accuracy issue. Discussion on entry 2. * Note that ARS was undertaken until 2018 so updated info is available. Discussion on entry 3. * Should data be validated before disclosure – is the intent that the data is formatted properly, or is the suggestion to have it verified? This would delay the disclosure process. Is that something that has been considered as in the case of verification the registrant has 15 days to respond. It would also call attention to the registrant that his/her information is being queried. If a registrar has a 30 day turnaround time, it may not impact the overall timeline for disclosure? But good point that would need further consideration if it is to be further pursued. Discussion on entry 4. * None GAC input questions * By how and by whom can it be measured: what is the relevance of SAC058? Even though it is not recent, it is still considered valid by the GAC. * Have been doing best to find reports and data to corroborate arguments, such as most recent ARS report and the Interisle study, but there are then questions raised about the validity of these. Need to have constructive discussion on what data is accepted / recognized. Would also like to see data that points to the contrary. * Section 7.3.2 of RAA – example was perceived by some as contrary, but need to take everything into account including ICANN Bylaw requirement. Some would like some follow up discussion on the holistic aspect. Not about dictating an outcome, but it is about taking an open approach and making sure that whole picture is known. For example, there may be specific accuracy requirements in certain legislations that are not known. * Suggestion – now that homework has been completed on the gap analysis, would it be possible for the staff team to go through and pick out the specific references to evidence / reports of data. Put the data in front of everyone and talk about it. Action item: Leadership team to further consider proposal to pull the hard data out of the gap analysis input received to allow for review and discussion by the Scoping Team during upcoming leadership meeting. 1. Measurement of accuracy (60 minutes) – (20 minutes) * Review ICANN Org Memo – ARS Overview<https://community.icann.org/download/attachments/184996761/ICANN%20Org%20Me…> * Overview of memo provided by ICANN org * Q & A * Different layers to it, understanding a snapshot, what are the measures to put in place to improve or assure that registration data is accurate. Both important aspects of the scoping team’s work – what are the accuracy levels currently, what are the current requirements and are those being met, are there ways to improve on it. * Regarding the costs – each of these ARS studies averaged 200,000 – 250,000 USD. While that is not insignificant but if you compare this to other expenses it may not be outrageous or prohibitive as many did see value in ARS. * ICANN org does need to be in compliance with GDPR and work with its CPs to make sure that data can be processed in a legal fashion. Most recently adjustments have been made in the context of DAAR for access to data, so there is precedent for having this type of negotiations. * There is a lot of flux in data protection legislation such as for example international transfers but a lot is being done in the business world to adjust to those new regimes. Why are hands being thrown up instead of trying to find work arounds? * If there are further questions from the group on the memo, please put these in writing so that ICANN org can take these back. * Lack of data processing terms and conditions between ICANN org and CP is an hinderance. Action item: Team members to review ARS memo and identify any further follow up questions they may have. * Review input received on google doc<https://urldefense.com/v3/__https:/docs.google.com/document/d/11msexuoqWSUs…>, see page 25 - How and by whom can it be measured whether current goal(s) of existing accuracy requirements are met? * Confirm next steps 1. Confirm action items & next meeting (Thursday 3 February at 14.00 UTC)

1 0

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

Jan. 27, 2022

Dear all, All recordings for the Registration Data Accuracy Scoping Team held on Thursday, 27 January 2022 can be found on the agenda wiki page <https://community.icann.org/x/9ID3Cg> (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, 03 February 2022 at 14:00 UTC
by Terri Agnew Jan. 27, 2022

Jan. 27, 2022

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 03 February 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/94D3Cg * Check your time zone: https://tinyurl.com/2p84k6aa 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, 27 January 2022 at 14:00 UTC
by Terri Agnew Jan. 27, 2022

Jan. 27, 2022

**starting in 15 minutes 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 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/4h5xsj8t__;!!PtGJab4!qBJappc…> 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

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

Jan. 26, 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 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/4h5xsj8t__;!!PtGJab4!qBJappc…> 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 #15 on Thursday 27 January at 14.00 UTC
by Marika Konings Jan. 25, 2022

Jan. 25, 2022

Dear All, Please find below the proposed agenda for the next meeting of the Registration Data Accuracy Scoping Team which has been scheduled for Thursday 27 January at 14.00 UTC. As a reminder: 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/e…<https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit?p…>. Best regards, Caitlin, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #15 Thursday 27 January at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * Assignment 1 write up 1. Gap Analysis (10 minutes) * Finalize review of input: https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit * Scoping team input * Confirm next steps 1. Measurement of accuracy (60 minutes) – (20 minutes) * Review ICANN Org Memo – ARS Overview<https://community.icann.org/download/attachments/184996761/ICANN%20Org%20Me…> * Q & A * Review input received on google doc<https://docs.google.com/document/d/11msexuoqWSUsFj8ZjVvWF-XHpcMJntWH/edit>, see page 25 - How and by whom can it be measured whether current goal(s) of existing accuracy requirements are met? * Confirm next steps 1. Confirm action items & next meeting (Thursday 3 February at 14.00 UTC)

1 0

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