[GNSO-EPDPP2-SmallTeam] EPDP Phase 2 Small Team Update

[Marika Konings]

Thanks, Marc. I’ve made some proposed updates to the letter to reflect your suggestion (see attached). If that is not what you had in mind, please feel free to suggest further edits.

All, if you have any further input on the proposed letter, please share this by COB today, Monday 28 February, so it can be shared next with the GNSO Council for its review in order to be able to send the letter to the Board by the end of this week.

Best regards,

Marika

From: GNSO-EPDPP2-SmallTeam <gnso-epdpp2-smallteam-bounces at icann.org> on behalf of "Anderson, Marc via GNSO-EPDPP2-SmallTeam" <gnso-epdpp2-smallteam at icann.org>
Reply to: "Anderson, Marc" <mcanderson at verisign.com>
Date: Saturday, 26 February 2022 at 00:29
To: "Sebastien at registry.godaddy" <Sebastien at registry.godaddy>, "gnso-epdpp2-smallteam at icann.org" <gnso-epdpp2-smallteam at icann.org>
Subject: Re: [GNSO-EPDPP2-SmallTeam] EPDP Phase 2 Small Team Update

Sebastien,

Thank you for the email update.  This makes sense and at least for me helps set expectations for what is expected and when.

I like your suggestion about having the small team meet directly with the board GDPR caucus.  I wasn’t on the Rec 12 small team, but I understand that having direct conversation with the board, council and working group representatives was key to moving that forward.  The suggestion is in line with what was discussed during the 27 Jan meeting between the board and council on the SSAD ODA (https://community.icann.org/pages/viewpage.action?pageId=184997209).  At the end of the call Maartin noted that he is open to having more discussions rather than just exchanging letters with positions, with Philippe agreeing to more informal discussions trying to move things forward as opposed to correspondence.

I have no concerns with the proposed letter but have a suggestions for consideration.  It ends with this sentence:

Until that time, we do hope to keep channels of communication open and if necessary, to schedule further conversations to come to a mutually agreeable approach on the next steps in this important process.

Given your suggestion, I wonder if it makes sense to expand on that a little bit.  Instead of hoping to keep channels of communication open and if necessary schedule further conversations, lets take the next step and suggest scheduling those conversations.

Best,
Marc


From: GNSO-EPDPP2-SmallTeam <gnso-epdpp2-smallteam-bounces at icann.org> On Behalf Of Sebastien at registry.godaddy
Sent: Friday, February 25, 2022 5:35 AM
To: gnso-epdpp2-smallteam at icann.org
Subject: [EXTERNAL] [GNSO-EPDPP2-SmallTeam] EPDP Phase 2 Small Team Update


Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Dear All,

Thank you to those who were able to provide initial input by the deadline and thank you to those who are still working on it. I appreciate that there is a lot of information to digest and consultations to undertake with your respective groups. As was previously indicated, this input is not expected to be the final determination by the small team, but the idea was that it would provide some initial indications of the common as well as different views that would allow the GNSO Council to provide the ICANN Board with a high-level update during its joint session at ICANN73.

At the same time, there is an expectation that the small team will be able to provide its input to the GNSO Council as soon as feasible as this is just the first step in a longer process. As such, I would like to suggest proposing the following to the GNSO Council with regards to next steps and timeline:

Date

What

Whom

Wednesday 2 March

Initial reactions to google doc questions (Q1-7)

Small team (those that have not provided input yet)

Friday 4 March

Questions concerning ODA (Q.A-C)

Small team (those that have not provided input yet)

Thursday 4 March

Share high level summary of responses to google doc questions with small team for review (Q1-7)

Sebastien Ducos

Friday 5 March

Share high level summary of responses to google doc questions with GNSO Council (Q1-7)

Sebastien Ducos

Tuesday 8 March

Share high level summary of responses during ICANN Board – GNSO Council session (noting that this is initial input that the Council will need to consider further)

Sebastien Ducos

Wednesday 9 March

GNSO Council Meeting – update on small team progress and debrief from Council – Board meeting

GNSO Council

By 31 March

Small team to finalize its input to the GNSO Council

Small Team

14 April

GNSO Council meeting - Council to review small team input and determine response to the ICANN Board / next steps

GNSO Council

19 May

(if necessary) GNSO Council meeting - Council to review small team input and determine response to the ICANN Board / next steps

GNSO Council


Note that I do not anticipate that the work of the small team will end by 31 March. As also noted previously, regardless of the path that is ultimately chosen, whether the Board makes a determination next on whether or not to adopt all or part of the recommendations or whether the Council decides to undertake further work on the recommendations, there is a likely role for the Council to take a further look at the recommendations themselves. I anticipate that the Council will continue to lean on the expertise of this small team to assist with such an effort. I am of the view that such further consideration would benefit from informal interaction with interested Board members. This has proven to be very beneficial in instances where the ICANN Board has expressed concerns as recent experience in the context of the EPDP Phase 1 recommendation 12 demonstrated. Of course, we are already benefiting from the participation of Becky in the small team, as the Board liaison to the EPDP Phase 2, but maybe informal interaction could be considered between the small team and the Board GDPR Caucus to better help inform further consideration of potential changes / modifications. Before sharing this suggestion with the Council, I would appreciate hearing your feedback on this idea.

In preparation for ICANN73, Council leadership would like to provide the ICANN Board with an update on the work that has been undertaken to date as well as expected next steps & timing. Please find this in the proposed draft message attached. I plan to share it with the GNSO Council for its review on Monday.

I hope this approach can count on your support. As always, please feel free to share your comments and suggestions.

Kindly,
Sebastien





Sebastien Ducos
GoDaddy Registry | Senior Client Services Manager
[signature_1709708321]
+33612284445
France & Australia

sebastien at registry.godaddy<mailto:sebastien at registry.godaddy>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/gnso-epdpp2-smallteam/attachments/20220228/99b5fb08/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 8206 bytes
Desc: image002.png
URL: <https://mm.icann.org/pipermail/gnso-epdpp2-smallteam/attachments/20220228/99b5fb08/image002-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Proposed response to the ICANN Board - updated 28 February 2022.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 15878 bytes
Desc: Proposed response to the ICANN Board - updated 28 February 2022.docx
URL: <https://mm.icann.org/pipermail/gnso-epdpp2-smallteam/attachments/20220228/99b5fb08/ProposedresponsetotheICANNBoard-updated28February2022-0001.docx>