April 2022 - GNSO-Accuracy-ST

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

April 28, 2022

Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 05 May 2022 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/94504686990?pwd=MWc2eXZE…> Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd <https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, alternates and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/RQ51Cw * Check your time zone: https://tinyurl.com/2x244etm 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

CANCELLED | Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 28 April 2022 at 14:00 UTC
by Terri Agnew April 28, 2022

April 28, 2022

**This meeting has been cancelled, please remove it from your calendars Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 28 April 2022 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/94504686990?pwd=MWc2eXZE…> Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd <https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, alternates and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/Qw51Cw * Check your time zone: https://tinyurl.com/248yw48c [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/248yw48c__;!!PtGJab4!oOHI15S…> 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

Canceled: Registration Data Accuracy Scoping Team meeting
by ICANN Policy Calendar April 28, 2022

April 28, 2022

Meeting: Registration Data Accuracy Scoping Team meeting Date/time: Recurring weekly on Thursdays at 14:00 UTC for 90 minutes, 21 April – 09 June 2022 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 2022 Wiki agenda pages: https://community.icann.org/x/7ID3Cg (see dates on the left column) * Check your time zone: https://tinyurl.com/staz76cv 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://forms.gle/GZqMAi4kKDaVP5o66> 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.

1 0

Cancellation of today's meeting - Re: Proposed Agenda - Registration Data Accuracy Scoping Team meeting #27 on Thursday 28 April at 14.00 UTC
by Marika Konings April 28, 2022

April 28, 2022

Dear All, Due to unforeseen circumstances, we need to cancel today’s meeting. However, in order to take advantage of the time that you had already set aside for this meeting, we would like to encourage you to commence your review of the write up for assignments #1 and #2 (see https://docs.google.com/document/d/13sP-2z7rusEYrDyntrgm-tcIavPMJndU/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/13sP-2z7rusEY…>) and flag any issues / comments / suggestions you may have (in the form of comments) by Wednesday 4 May. Similarly, if there are any follow up questions to the responses that were provided by ICANN Compliance (see https://mm.icann.org/pipermail/gnso-accuracy-st/2022-April/000398.html) please share these with the list so that these can be considered during next week’s meeting. Best regards, Caitlin, Berry and Marika From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces(a)icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Tuesday, 26 April 2022 at 15:49 To: "gnso-accuracy-st(a)icann.org" <gnso-accuracy-st(a)icann.org> Subject: [GNSO-Accuracy-ST] Proposed Agenda - Registration Data Accuracy Scoping Team meeting #27 on Thursday 28 April at 14.00 UTC Dear All, Please find below the proposed agenda for the next Registration Data Accuracy Scoping Team meeting which will be chaired by Olga Cavalli as Michael Palage will be absent on Thursday. As a reminder: 1. RDA Scoping Team to begin reviewing Support Staff’s Initial Write-Up for the GNSO Council of Assignments 1 and 2 (see https://docs.google.com/document/d/13sP-2z7rusEYrDyntrgm-tcIavPMJndU/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/13sP-2z7rusEY…>). 2. RDA Scoping Team to review the updates to the Gap Analysis Proposals (beginning on p. 8 of Google Doc) in preparation for next week’s meeting: https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit?p… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1sScP8MwgDCg4…>. Best regards, Caitlin, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #27 Thursday 28 April at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * ICANN Compliance team to join meeting on 5 May to discuss Registrar Audit Proposal 1. Write up for assignments #1 & #2 (see https://docs.google.com/document/d/13sP-2z7rusEYrDyntrgm-tcIavPMJndU/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/13sP-2z7rusEY…>) (15 minutes) * High level overview * Initial reactions * Discuss timeline for review and how to deal with placeholders * Confirm next steps 1. ICANN org responses to recent set of questions (see https://mm.icann.org/pipermail/gnso-accuracy-st/2022-April/000398.html) (15 minutes) * Reactions / follow up questions * Confirm next steps 4. Overview of progress made on Gap Analysis Data Collection Proposals (30 minutes) (see https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1sScP8MwgDCg4…>) a. High level overview b. Initial reactions c. Confirm next steps 1. Confirm action items & next meeting (Thursday 5 May at 14.00 UTC)

1 0

**REMINDER** Meeting invitation | Registration Data Accuracy Scoping Team | Thursday, 28 April 2022 at 14:00 UTC
by Julie Bisland April 27, 2022

April 27, 2022

**Reminder, this meeting is for the entire team as the small team group has concluded. Dear all, The Registration Data Accuracy Scoping Team meeting is scheduled on Thursday, 28 April 2022 at 14:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94504686990?pwd=MWc2eXZENk9yN0RqOUUzaGx2eGV0QT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/94504686990?pwd=MWc2eXZE…> Passcode: Vc#0B7$pu8 For Audio only: Or One tap mobile : US: +13017158592,,94504686990#,,,,*4631547480# or +13126266799,,94504686990#,,,,*4631547480# Webinar ID: 945 0468 6990 Passcode: 4631547480 International numbers available: https://icann.zoom.us/u/akRu7JTFd <https://urldefense.com/v3/__https:/icann.zoom.us/u/akRu7JTFd__;!!PtGJab4!pY…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, alternates and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/Qw51Cw * Check your time zone: https://tinyurl.com/248yw48c [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/248yw48c__;!!PtGJab4!oOHI15S…> 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 #27 on Thursday 28 April at 14.00 UTC
by Marika Konings April 26, 2022

April 26, 2022

Dear All, Please find below the proposed agenda for the next Registration Data Accuracy Scoping Team meeting which will be chaired by Olga Cavalli as Michael Palage will be absent on Thursday. As a reminder: 1. RDA Scoping Team to begin reviewing Support Staff’s Initial Write-Up for the GNSO Council of Assignments 1 and 2 (see https://docs.google.com/document/d/13sP-2z7rusEYrDyntrgm-tcIavPMJndU/edit) 2. RDA Scoping Team to review the updates to the Gap Analysis Proposals (beginning on p. 8 of Google Doc) in preparation for next week’s meeting: https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit?p…. Best regards, Caitlin, Berry and Marika Registration Data Accuracy Scoping Team – Meeting #27 Thursday 28 April at 14.00 UTC 1. Welcome & Chair Updates (5 minutes) * ICANN Compliance team to join meeting on 5 May to discuss Registrar Audit Proposal 1. Write up for assignments #1 & #2 (see https://docs.google.com/document/d/13sP-2z7rusEYrDyntrgm-tcIavPMJndU/edit) (15 minutes) * High level overview * Initial reactions * Discuss timeline for review and how to deal with placeholders * Confirm next steps 1. ICANN org responses to recent set of questions (see https://mm.icann.org/pipermail/gnso-accuracy-st/2022-April/000398.html) (15 minutes) * Reactions / follow up questions * Confirm next steps 4. Overview of progress made on Gap Analysis Data Collection Proposals (30 minutes) (see https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit) a. High level overview b. Initial reactions c. Confirm next steps 1. Confirm action items & next meeting (Thursday 5 May at 14.00 UTC)

1 0

Registration Data Accuracy Scoping Team meeting
by ICANN Policy Calendar April 26, 2022

April 26, 2022

Meeting: Registration Data Accuracy Scoping Team meeting Date/time: Recurring weekly on Thursdays at 14:00 UTC for 90 minutes, 21 April – 09 June 2022 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 2022 Wiki agenda pages: https://community.icann.org/x/7ID3Cg (see dates on the left column) * Check your time zone: https://tinyurl.com/staz76cv 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://forms.gle/GZqMAi4kKDaVP5o66> 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.

1 0

Notes and action items - RDA Scoping Team Meeting #26 - 21 April 2022
by Caitlin Tubergen April 22, 2022

April 22, 2022

Dear RDA Scoping Team, Please find below the notes and action items from yesterday’s meeting, which was repurposed as a Small Team meeting. The next plenary meeting will be Thursday, 28 April at 14:00 UTC. Best regards, Marika, Berry, and Caitlin -- Action Items 1. RDA Scoping Team to begin reviewing Support Staff’s Initial Write-Up for the GNSO Council of Assignments 1 and 2. Full RDA Scoping Team to discuss needed timeline for review during the next meeting. 2. Owen to recirculate previous message regarding Whois Inaccuracy Complaint data for the team to review and see if anything else is needed from ICANN Compliance. (Note: completed 21 April) 3. Brian G. to check with ICANN org colleagues if there is (i) any additional publicly-available data that has not already been shared that the group could review and (ii) if the compliance auditing subject matter experts are available to attend next week’s call to discuss further details/answer questions regarding a potential accuracy-based audit. 4. Support Staff to work with IPC colleagues on open question for Proposal H. (Note: completed 21 April). 5. RDA Scoping Team to review the updates to the Gap Analysis Proposals (beginning on p. 8 of Google Doc) in preparation for next week’s meeting: https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit?p…. 21 April 2022 RDA Scoping Team Small Team Call * Earlier this week, Support Staff shared a proposed write-up for the GNSO Council for assignments 1 and 2. * The write-up was circulated as a Google Doc – please feel free to provide suggestions and edits in the form of comments: https://docs.google.com/document/d/13sP-2z7rusEYrDyntrgm-tcIavPMJndU/edit * The deadline for review will ultimately be up for the full group to weigh in on. * During next week’s meeting, with the full team, the group should discuss the outreach ICANN org is planning to the EDPB and how that could affect the timeline. Similarly, can any of the proposals kick off in the meantime? Perhaps there would be a logical break in meetings while data is gathered. * Perhaps for the proposals that do not require personal data, the group can close on those today. In short, the group can document in further detail what these proposals would entail. The group would then determine which proposals could be sent to the Council. * An RDA Scoping Team meeting is included on the draft schedule for ICANN74, but it is still a draft. * Next week, the group can discuss how it would like to use this time. * It could be a chance to present the proposals to the GNSO Council, for example * During last week’s meeting, the group made substantial progress on Proposal A, in large part because of the CPH contributions. Support Staff made several updates based on last week’s conversations; encourage the group to read Support Staff’s additions to confirm the accuracy. Proposal E – Review of Accuracy Complaints * To further detail the proposal, a few items the group may wish to consider: (i) What information is the group expected to learn from the review of these complaints and how would that help inform the deliberations of the group; (ii) a practical way forward may be to review the information that is already available * Expectation is the ST would understand what type of complaints are sent to ICANN Compliance and what the outcome rates are (for different possible outcomes) Could follow these steps: * Gather all complaints in any category related to registration data accuracy * categorize each complaint: * group into categories (validation, verification, inaccuracy, other?) * assign an outcome status (corrected, suspended, confirmed as already accurate, etc) * Evaluate rates * It may be helpful to contextualize the ICANN org complaints – for example, could be helpful to include the bigger picture, i.e., out of the total complaints, how many are are related to accuracy? * Approximately six months ago, Owen previously looked at all of the published complaint data going back to 2013 re: total number of Whois inaccuracy complaints and the various subtypes * Action: Owen to recirculate this email so that it at the top of the team’s mailing list. Note: completed – RDA Team to refer to Owen’s recent email * One problem – if the domain name is removed from the zone, the ticket is closed. In other words, just because a ticket is closed does not mean a full investigation has been completed of the inaccuracy complaint. * Action Item: Support Staff to check with ICANN org colleagues if there is any additional publicly-available data that has not already been shared that the group could review * Question for the group: this will require review and analysis – is this something the team as a whole should be doing? Or would a small team of volunteers review the information once it is shared? Proposal A – Registrar Survey * The idea of the survey was shared with the RrSG as something the RDA Scoping Team has been discussing, but this has not been discussed in detail yet * This will be helpful in vetting this with GNSO Council if the idea has been shared and garnered informal support from the RrSG * Believe there could be some valuable input that registrars could provide. Once this group has come up with the questions, it seems like something ICANN org could do, rather than hire an outside company. This should not be a high cost. * Proposal D – Registrar Audit * As you may recall, Request further information from ICANN org what information could be audited and in what timeframe. Important for the scoping team to understand what information might result from an audit to determine if/how it can inform the deliberations. * Compliance colleagues have offered to provide follow-up information on the provided answers (if any) * Based on the feedback provided by Compliance, is this an avenue the team would like to pursue? * The response indicates that an audit can take two months to kick off; the selection criteria would need to be established. * Seems that ICANN org is awaiting more input (from the EDPB, for example) before delving into the processing of redacted data. Would ICANN Compliance be willing to work with this team on an accuracy-related audit? * Dispel the impression that an audit will would fix all of the problems with data privacy/redaction. Data protection implications must be covered and reviewed. In previous audits, many registrars based in Europe have sent redacted answers to ICANN org. You cannot, for example, ask in an audit for issues or topics or questions that do not directly flow from the agreement, so if the registrar is not obliged to collect certain data under the RAA, then the audit cannot ask that. * Would be helpful to interact with compliance if there is staff expertise to design a study or audit * Brian to check with ICANN org colleagues, specifically the dedicated audit team, to see who the appropriate folks might be and get back to the group to see if engagement with this team is possible. * ARS would likely not be the outcome of a PDP, as ARS was not based on a previous PDP. * To put it in context, what we asked groups to do is to identify how current requirements are being met and how that can be measured. The idea is based on that measurements, we would then kind of move into Assignments 3 and 4 and review now that the group has relevant data, does it demonstrate any kind of gaps that need to be further investigated, either through a PDP or other means? If yes, those would then be recommendations and go back to the Council. At this stage, we cannot say if the recommendations would be based on consensus of this group or if it would just be documented as different perspectives from the team. * Action: Support Staff to reach out to Lori S. to review the outstanding question to IPC, and Lori to answer the question by the end of the week.

1 0

Potential Additional Data Points for the Groups Consideration
by Michael Palage April 22, 2022

April 22, 2022

Hello All, Thanks for another productive small team meeting yesterday. As we move forward with drafting a report to the GNSO Council regarding our work in connection with Assignments 1 & 2, and how that may impact our future working regarding Assignments 3 & 4, I wanted to share some information that may be of interest to the members within the Group. Attached is a slide deck that Hans Seeuws from EURid said I could share with the Accuracy Scoping Working Group regarding EURid’s work to increase the accuracy of registrant data through their KYC initiative. This deck is based upon a similar presentation that Hans gave at a recent CENTR meeting. While I fully support the work that EURid is doing in this area, I have personally advocated the use of an alternative term given than KYC implies a very heightened level of verification on par with the banking system. I have often used KYR (Know Your Registrant). I believe the European ccTLDs have been doing some ground breaking work in the area of developing proportionate registrant verification practices and I think there are some lessons to be learned and perhaps some best practices to be implemented from our European ccTLD colleagues. I know there was a previous discussion regarding how the cross field validation requirements contained in the 2013 RAA have never been implemented because of perceived cost issues. However, I think this provides an interesting data point on how some in the domain name ecosystem are engaged in some creative thinking. As we move forward with potential surveys to Registrars involving NON PII data, I came across this provision in the Nominet Registrar Accreditation Agreement that may be another data point for our consideration. According to the Nominet’s RRA, Paragraph E.1.4 of Schedule 1 in the RRA states that “that you [Registrar] have a process in place for data quality validation, which complies with our Data Quality Policy, and which is auditable by us [Nominet].” Per Nominet’s Data Quality Policy, for Accredited Channel Partner Tag holders, these must be “written processes.” See https://nominet.uk/wp-content/uploads/2018/09/13094001/Data-Quality-Policy.… Therefore, I think it would be highly informative to know how these written Data Quality Processes stack up against the 2013 RAA Accuracy requirements. Best regards, Michael

2 1

Fwd: ICANN Compliance data re: whois related complaints
by Owen Smigelski April 21, 2022

April 21, 2022

Hi all, As requested on this morning’s call, I am sharing the data I collected regarding all whois related complaints reported by ICANN Contractual Compliance between 2012 to 2021. Please see the explanation below regarding my analysis and formatting. There were a total of 242 whois QR complaints (versus 198,688 whois inaccuracy complaints). The link is shareable and anyone can leave comments if there are any questions (and also happy to answer questions via email or a future meeting). Regards, Owen > Begin forwarded message: > > Hi Accuracy Scoping Team leadership, > > The CPH team has been considering additional metrics/data that could help guide the scoping team’s work. One relevant data point we considered is ICANN Compliance data regarding whois related complaints. Because of my experience creating and refining these metrics, I volunteered to compile them. We think that the results may benefit our work, and wanted to provide the data to you for review/consideration first. > > Here is a link to a Google Sheet of the data: > > https://docs.google.com/spreadsheets/d/1qj6mjk-uR6YQbum5k6Y5sH8Hk0JDJDHCdwC… > > The “Summary” tab includes all whois inaccuracy complaints filed by year from 2012 to December 2021 (the last month available). The “Raw Data” tab is all of the data from icann.org, including links to each report cited. I included all whois related complaints (such as whois unavailable and whois format) because sometimes those complaint types receive inaccuracy allegations). > > For the summary, I only totaled the whois inaccuracy complaints. I also did not include complaints that were closed before 1st notice in the summary, as those are closed as out of scope (not about actual inaccuracy, no evidence, domain suspended at time of submission, etc). Whois QR and Whois ARS tickets are not included in the annual totals as well. > > Although the numbers fluctuate between 2012 and 2017, the total volume begins to drop significantly at the beginning of 2018 (before the effective date of the GDPR). There is another significant drop in September 2020, which I think is the month that Compliance switched from Kayako to NSp. > > Although the CPH is not clear what conclusions may be drawn from this data, we think this is something that should be shared with the entire scoping team (and be incorporated into our report). Happy to answer any questions, or provide an editable version (I have a few formals in the sheet that I don’t want modified). > > Regards, > > Owen > (On behalf of the CPH scoping team) >

1 0