[Gnso-epdp-team] The final stretch

[Janis Karklins]

Hi Matt,

In the Agenda for tomorrow's meeting you can see the outline of the process
until the end of July. This week is final for deliberations. Some time is
needed to put things together, then read it for the last time before
proceeding with consensus determination. Hence, the countdown has started.
If we can't agree this week after more than a year of process, there is no
guarantee that few additional weeks will help. The Team was told about 30
June deadline for past 6 months. Nobody can say that they have been taken
by surprise with 30 June deadline.

Therefore, my appeal to the Team members - be focused on outstanding issues
and compromise. It is time.

See you tomorrow
JK

On Mon, Jun 29, 2020 at 6:07 PM Matt Serlin <matt at brandsight.com> wrote:

> Hi Janis (and team),
>
>
>
> One positive of a virtual ICANN meeting is no jetlag so recovery seemed
> much easier this time 😊
>
>
>
> Wanted to just ask a few questions on your note below to make sure I’m
> understanding everything correctly so if either Janis or staff could
> clarify, I’d greatly appreciate it…
>
>
>
>    - I thought we had been given an additional month (end of July) by the
>    GNSO council to conclude our work? I understand Janis we will be losing you
>    as our leader later this week, but I thought the plan was for Rafik to take
>    over for the remainder of our time to get our work completed.
>    - Perhaps I’m reading your message incorrectly, but I believe it’s
>    entirely possible we could complete our work without agreement on ALL
>    topics, but still have a final report that included a number of
>    recommendations that would have achieved consensus within the group.
>    Obviously we are continuing to work on some of those stickier issues, but I
>    believe it’s entirely possible for us to wrap up Phase 2 without agreement
>    on everything so that whatever is included in the final report would be
>    what’s presented to Council and ultimately the Board.
>    - Speaking on consensus, it’s not clear to me when we are going to
>    proceed with doing a consensus call by all parties as we look to wrap up
>    Phase 2. I think this is something we should plan to discuss in our
>    meetings this week unless it’s clear to everyone else. And perhaps
>    clarification on point one above will make this more clear.
>
>
>
> And finally, I just wanted to thank you Janis for all of your leadership
> throughout this process as you wrap up your service this week regardless of
> the outcome. You’ve put in a tremendous amount of work to get us to this
> point and we all owe you our gratitude.
>
>
>
> Best regards,
>
> Matt
>
>
>
>
>
> *From: *Gnso-epdp-team <gnso-epdp-team-bounces at icann.org> on behalf of
> Janis Karklins <karklinsj at gmail.com>
> *Date: *Monday, June 29, 2020 at 2:51 AM
> *To: *EPDP <gnso-epdp-team at icann.org>, "gnso-epdp-lead at icann.org" <
> gnso-epdp-lead at icann.org>
> *Subject: *[Gnso-epdp-team] The final stretch
>
>
>
> Dear Team members,
>
>
>
> I hope that you have recovered from the ICANN 68.
>
>
>
> This message is to remind that we are at an important juncture - to
> finalize a compromise agreement or to acknowledge the failure to agree.
>
> It is of utmost importance to provide comments on suggested recs -
> Automation and mechanism - by end of today. So far no reaction has been
> received. It would allow us to understand whether agreement is in the reach
> or not really.
>
>
>
> As you know my availability ends on 30 June. I am prepared to add two
> additional meetings this week if the objective is attainable and everyone
> is committed to work towards a consensus proposal. Otherwise, I will
> propose to stop consideration of the Report and to acknowledge the lack of
> agreement and failure of the Team with all subsequent consequences.
>
>
>
> I am in your hands, dear Team members.
>
>
>
> Best regards
>
> JK
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-epdp-team/attachments/20200629/84a2ab56/attachment-0001.html>