2022-03-31 Registration Data Accuracy Scoping Team- Meeting #23

PROPOSED AGENDA

1. Welcome & Chair Updates (5 minutes)

2. Commence deep dive of Gap Analysis Data Collection Proposals (60 minutes)(see https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit[docs.google.com])

   1. Proposal A – Survey Registrars

   2. Proposal B – Third Party Assessment (if time allows)

   3. Proposal D – ICANN org Registrar Audit (if time allows)

   4. Proposal E – Review of Accuracy Complaints (if time allows)

   5. Confirm next steps

3. Accuracy description of current requirements and enforcements (15 minutes)

   1. Review input received on proposed description of current accuracy requirements and enforcement (see https://docs.google.com/document/d/1e5rUm-AFFDgNOU3OcT7ABu4InGwPiUyb/edit [docs.google.com])

   2. Confirm next steps

4. Confirm action items & next meeting (Thursday 7 April at 14.00 UTC) 

BACKGROUND DOCUMENTS

PARTICIPATION

Apologies: Lori Schulman, Steve Crocker, Becky Burr

Alternate: none

RECORDINGS

Audio Recording

Zoom Recording

Chat Transcript 

GNSO transcripts are located on the GNSO Calendar

Notes/ Action Items

Action Items

1. Scoping Team to continue the deep dive review of the Gap Analysis Proposals (beginning on p. 8 ofGoogle Doc [docs.google.com]) to identify relevant mitigation to noted downsides and next steps (by whom, by when, other considerations). Please populate additional thoughts to discuss during the next meeting by Wednesday, 6 April 2022.

2. Michael to confirm to the list if/how to proceed with a small team to work out more details for Proposal A (registrar survey) by Monday, 4 April.

3. Scoping Team Members to review the description of current accuracy requirements and enforcement, particularly the new updates, and try to resolve outstanding issues on list among the interested members/conflicting opinions. Deadline for updates is COB Wednesday, 6 April 2022.

4. STILL OUTSTANDING: IPC Reps: please respond to the comments directed to you in Proposal H in theGap Analysis Doc [docs.google.com].

Registration Data Accuracy Scoping Team – Meeting #23

Thursday 31 March at 14.00 UTC

1. Welcome & Chair Updates (5 minutes)

   • It would be helpful to understand how many members are anticipating attending ICANN74 physically

   • Some members are still unsure

   • What may be helpful – Support Staff will send a doodle poll to determine who will attend in person vs. who will attend virtually (or not at all). This is helpful in determining if there will be an Accuracy session at ICANN74.

   • Where is ICANN org on the communication to the DPA?

   • ICANN org is planning to engage European DPAs regarding next steps that can be taken with respect to registration data accuracy. ICANN org will consult with the Board through this process. Plan is to follow up with the European Commission soon – will likely have more information to share later this week.

   • Some updates were made to the data accuracy description prior to the call; plan to stick with the agenda for now. If time allows, members who made updates can speak to the changes later in the call.

2. Commence deep dive of Gap Analysis Data Collection Proposals (60 minutes)(see https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit [docs.google.com])

- As discussed during the last meeting, the team went through the proposals at a high-level. It is now time to go through the proposals more closely to determine the viability of the proposals, and, ultimately, to determine which proposals to pursue.

- Support Staff developed a template to synthesize the general idea behind the proposal (what is this about?), what were the noted upsides and downsides – groups may wish to consider how downsides can be mitigated, and lastly, how to drill down on next steps.

- For each proposal, there were some preliminary next steps noted. Now the group will need to see who will be responsible for the next step, expected timeframe, and what considerations should be included.

          a. Proposal A – Survey Registrars

      b. Proposal B – Third Party Assessment (if time allows)

• Is this expected to generate more or better information than the registrar survey?

• A third-party assessment may slow things down and cost more money

• This is mislabeled – the numbers would still have to be extracted from a registrar, and the third party would not have the ability to audit the data. It may increase participation, but it’s not an assessment. Adding an intermediary that is paid may result in slightly more data or slightly less data. Accordingly, see very little value in pursuing this further.

• There would be better data quality if you hire an independent contractor who is skilled in data assessment, this could be easier; will have better data uniformity if you hire an independent contractor familiar with quality measurement. The goal of hiring someone would be to make it easier on registrars.

• Third party may drop the participation as some registrars may be more inclined to respond to an RrSG survey

     c. Proposal D – ICANN org Registrar Audit (if time allows)

• This seems to be something that could be Assignment 3 or 4 work

• If results will not be available in a 2022 timeframe, it is likely not valuable to this group for answering assignment #2

     d. Proposal E – Review of Accuracy Complaints (if time allows)

     e. Confirm next steps

    3. Accuracy description of current requirements and enforcements (15 minutes)

   4. Confirm action items & next meeting (Thursday 7 April at 14.00 UTC)