Dear all,

 

Unfortunately my meeting ran late yesterday and I could not join the first part of the discussion. When I joined I realized that the meeting ended sooner than usually.

 

I was a bit surprised to see that despite the wide consensus our suggested changes were not taken into account. We were very explicit from the beginning that deleting the reference “not limited to” is dependent on moving part of the footnote in the main text.

 

It is difficult to agree on this version of the text as it currently stands so I hope we can liaise with CPH still today in an effort to resolve this.

 

On a separate note, I understand that the next accuracy scoping team meeting coincides with the GAC WHOIS session at which I am presenting. Given that it will be impossible to duplicate my presence I hope that it is feasible to change the time of the accuracy scoping meeting as it is in many colleagues’ interest to attend both sessions.

 

Best,

Melina

 

 

From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces@icann.org> On Behalf Of Marika Konings
Sent: Friday, June 10, 2022 9:52 AM
To: gnso-accuracy-st@icann.org
Subject: [GNSO-Accuracy-ST] Proposed Agenda - Registration Data Accuracy Scoping Team meeting #34 on Tuesday 14 June at 11.15 UTC

 

Dear All,

 

Please find below the proposed agenda for the next Registration Data Accuracy Scoping Team meeting which is scheduled to take place during ICANN74 on Tuesday 14 June from 13.15 – 14.30 local time (11.15 – 12.30 UTC).

 

As discussed during yesterday’s meeting, the staff support team has gone ahead and created a consolidated version of the write up which can be found here: https://docs.google.com/document/d/1cV5ExSZD6G-owksGmMEmig0OXVdGcAUU/edit?rtpof=true. All previous edits have been accepted and the staff proposed approach for remaining comments that were not challenged have been applied. For those interested in seeing a redline version, you can find in the archive folder a document that compares the 20 April version with today’s version. We’ve left the two remaining items to be resolved in the document in the form of comments and would like to encourage everyone to come prepared to resolve these two items during the upcoming meeting.

 

As a reminder:

  1. GAC colleagues (or other members in agreements) to provide further information on what work could be done in the interim b/w assignments 2 and 3 instead of pausing work while additional data is collected/EDPB response is outstanding in advance of the next meeting on Tuesday, 14 June.
  2. Laureen K. to populate newly-introduced proposal to register names with purposefully inaccurate information as an experiment into the proposal Google Doc: https://docs.google.com/document/d/1sScP8MwgDCg4yvFNAYwQVql7DQob60vX/edit [docs.google.com] in advance of the next meeting on Tuesday, 14 June.

Best regards,

 

Caitlin, Berry and Marika

 

 

Registration Data Accuracy Scoping Team – Meeting #34

ICANN74, Tuesday 14 June from 13.15 – 14.30 local time (11.15 – 12.30 UTC).

 

  1. Welcome & Chair Updates

 

  1. Brief recap
    1. Scoping Team assignment
    2. Current state of work
    3. planned outreach to the EDPB

 

  1. Finalize write up for assignments #1 and #2 for delivery to GNSO Council – see https://docs.google.com/document/d/1cV5ExSZD6G-owksGmMEmig0OXVdGcAUU/edit
    1. Consider any outstanding items

·         Scoping team recommendation #2 – what work, if any, can/should the Accuracy Scoping Team carry out while outreach to the EDPB is conducted, and/or based on what data can work on assignment #3 already begin?

·         Footnote page 10 – how to resolve

·         Any other proposals for data gathering that the Scoping Team should include for further consideration (e.g. register names with purposefully inaccurate information as an experiment)?  

    1. Confirm deadline for final review
    2. Confirm next steps

 

  1. Any other business

 

  1. Confirm action items & next meeting (TBC)