/
2022-05-26 Registration Data Accuracy Scoping Team- Meeting #31

2022-05-26 Registration Data Accuracy Scoping Team- Meeting #31

May 26, 2022

The Registration Data Accuracy Scoping Team call will take place on Thursday, 26 May 2022 at 14:00 UTC for 90 minutes.

For other places see:  https://tinyurl.com/2p8eap4f

PROPOSED AGENDA

  1. Welcome & Chair Updates (5 minutes)

  2. Scenarios for EDPB - see update from ICANN org (https://mm.icann.org/pipermail/gnso-accuracy-st/2022-May/000444.html) (15 minutes)

    1. Continue review of Scoping Team input (see https://docs.google.com/document/d/1rCBaQ175p_VrP6DtxLUuuoO9Uv5C2qp_/edit [docs.google.com]) 

    2. Confirm next steps

  3. Write up for assignments #1 & #2 (see https://docs.google.com/document/d/13sP-2z7rusEYrDyntrgm-tcIavPMJndU/edit[docs.google.com]) (30 minutes)

    1. Continue review of input received

    2. Confirm next steps

  4. Write up for Section 2.1.2 – Measurement of whether current goals are met (seehttps://docs.google.com/document/d/1CYs9mLHsKcZevmZtFrQBDXbv_nkQ5PKe/edit [docs.google.com]) (15 minutes)

    1. Review input received

    2. Confirm next steps

  5. Confirm action items & next meeting (Thursday 2 June at 14.00 UTC)

BACKGROUND DOCUMENTS



PARTICIPATION

Apologies: Lori Schulman, Sarah Wyld, Sophie Hey, Brian Gutterman, Steve Crocker, Marika Konings, Thomas Rickert

Alternate: Owen Smigelski, Alan Woods

Attendance

RECORDINGS

Audio Recording

Zoom Recording

Chat Transcript 

GNSO transcripts are located on the GNSO Calendar

Notes/ Action Items

Action Items

 

  1. EXTENDED: Scoping Team members to provide an update to their respective stakeholders group with respect to last week’s discussion about the draft EDPB communication, particularly with respect to scenario 2 and a data protection impact assessment (DPIA) of Scenario 2. Please provide any proposed updates by Wednesday, 1 June. https://docs.google.com/document/d/1rCBaQ175p_VrP6DtxLUuuoO9Uv5C2qp_/edit

  2. FINAL EXTENSION: Scoping Team members to review all comments received on the write-up and propose compromise language in comments form (where applicable) in advance by COB, Tuesday, 31 May. Please note this is the group's final opportunity to raise concerns with this document.https://docs.google.com/document/d/13sP-2z7rusEYrDyntrgm-tcIavPMJndU/edit [docs.google.com]. 

  3. FINAL EXTENSION: Scoping Team members to review the newly-circulated write up of C.2.2 and propose edits/comments in comment form by COB, Tuesday, 31 May. https://docs.google.com/document/d/1CYs9mLHsKcZevmZtFrQBDXbv_nkQ5PKe/edit [docs.google.com]. 

 

Registration Data Accuracy Scoping Team – Meeting #31

Thursday 26 May at 14.00 UTC



  1. Welcome & Chair Updates (5 minutes)

    • Registration for ICANN74 has been open, and the availability to sign up for sessions is now available. Please remember to register in advance and for individual sessions. In-person slots will be limited, so please sign up for the sessions in advance.



        2.Scenarios for EDPB - see update from ICANN org (https://mm.icann.org/pipermail/gnso-accuracy-st/2022-May/000444.html) (15 minutes)

  1.  

    1. Continue review of Scoping Team input (see https://docs.google.com/document/d/1rCBaQ175p_VrP6DtxLUuuoO9Uv5C2qp_/edit [docs.google.com])  

  1.  

    • There does not appear to be any new comments added as of our last meeting.

    • There is still no feedback from the GAC, IPC, BC – this is concerning

    • This is one of the most important things the group has been asked to consider during its deliberations.

    • Previous attempts by ICANN org to the Belgian DPA or EDPB have not resulted in actionable guidance that moved policy deliberations forward.

    • At a certain point in time, it’s important to make these interventions count. Accordingly, it’s important to make these deliberations count and position ICANN for success.

    • Alan G. – will flesh out

    • The original date was 23 May, we extended it to 27 May. How much time does the group need?

    • Proposal: this group will meet in person at ICANN74. Believe this is very important – accordingly, do we dedicate the meeting in the Hague to this communication?

    • Do not agree with this approach – do not believe this will be sent to the EPDB in the next two weeks. ICANN org still has a lot of work to do in terms of a DPIA, so the timing is not that critical. The Council instructions ask important questions that the group has yet to tackle – what should accuracy look like in the future?

    • Org spoke with the GAC earlier – for a variety of reasons, the instructions are still that ICANN needs to work through the EC and the Belgian DPA – the plan is to start those conversations quite soon; however, that does not mean there has to be a completed letter or DPIA at this time. Timing – would like to get started on this soon, but there will be parallel preparatory work done along the way.

    • In terms of making the most constructive use of face-to-face time: one issue the group has struggled with is what does accuracy mean? If we, in this group, cannot come to an agreement of what accuracy is – that would be a very important item for this group to opine on both to ICANN and the DPA.

    • In terms of making use of face-to-face time – one issue the group has not reached consensus on is what the term accuracy even means.

    • This is not the right question – we need to know what levels of accuracy are needed with respect to various elements in the RDDS

    • The two definitions that we had – binary (either inaccurate or accurate) or there are degrees of accuracy

    • On the last call, the group should support ICANN, but it is ultimately their work. Do not know if it is within the scope of this group to do this work. We have not seen a DPIA or received a request from ICANN. If members need more help giving generalized feedback to ICANN, a few more days should be helpful. In terms of the definition, the write-up shows the agreed upon description of accuracy and the proposals to gather more data to inform the current description. Believe we should focus on this before going to assignments 3 and 4.

               b.Confirm next steps

     3.Write up for assignments #1 & #2 (see https://docs.google.com/document/d/13sP-2z7rusEYrDyntrgm-tcIavPMJndU/edit [docs.google.com]) (30 minutes)

               a.Continue review of input received

            b.Confirm next steps

  1.  

    • Due to lack of homework, the same assignments will be extended (for the final time) until next week



      4.Write up for Section 2.1.2 – Measurement of whether current goals are met (see https://docs.google.com/document/d/1CYs9mLHsKcZevmZtFrQBDXbv_nkQ5PKe/edit [docs.google.com]) (15 minutes)



      5.Confirm action items & next meeting (Thursday 2 June at 14.00 UTC)