
33:04
Well, I usually forget, so thanks for the reminder

33:26
Thomas will be delayed and join in the second half

33:28
done

34:21
Hello all

34:42
Hi all.

37:22
May the final draft of questions be shared on-list?

37:46
Yes, of course, will do

37:51
Thanks, Becky.

42:40
So the proposal would be for this PDP to continue on after Phase 2?

43:34
@Matt: Or after the addendum to phase 2 has been published?

44:48
How can we bump two of the most difficult issues to a small group? And treat is as a comment?

45:23
Let me be clear, is this where we have arrived on this, or is the GNSO going to be deal with these two intractable issues?

46:05
@Janis: Yes, there was.

48:24
@Milton: +1.

48:45
The small group may consider looking at the legal advice we have paid for.

49:27
Also…, unless there is new input, I don’t see what this small group will be able to achieve. We’ve exhausted this topic to death, haven’t we?

50:05
@Volker: +1

50:16
@Amr, we have a new input in legal advice from Bird & Bird

50:29
+1 Milton and Volker

51:08
We may be hopelessly deadlocked on the topic, but since this is a charter issue it must be mentioned somewhere in our report

51:19
@MarkSV: +1

51:33
It will suffice to indicate that we are hopelessly deadlocked.

51:41
@Stephanie: +1

52:52
It’s unfortunate that text explaining the differences of opinions on the and other topics will not appear in the addendum. Isn't that a change on process? Asking for a friend

52:58
Minority Reports are to be attached to FINAL reports after consensus calls.

53:11
ok

53:14
I would add that we in all likelihood have different interpretations of the legal advice we are receiving at this late date. Had this EPDP taken the advice of the NCSG who recommended dedicated legal advice early on, we would not be in this rather desperate situation.

53:45
Which I will remind you has been very much impacted by the current COVID19 state of emergency.

54:12
it’s true, this is totally a policy difference

54:47
At least for some of us. Lucky are they who have not been impacted.

55:09
Dissent opinions can be expressed in the public comment.

55:49
We agreed on Tuesday that no group opinions would be included in this intial report and any disagreements would be done in the proceeding.

56:32
@Berry: True, but we also agreed that dissenting/minority statements will be included in the final report, correct?

56:55
is there some reason why the dissent has to be in initial report rather than final report?

56:56
Please double check

57:35
Well said Rafik!

57:54
No corona I hope?

58:54
Not so far, but we are not testing the relatively healthy.

59:11
Link to PDP manual. https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pdp-manual-24oct19-en.pdf

59:28
If the decision to NOT work on some items is not a CONSENSUS, why is it in the report?????????????????????????

59:36
@Janis, based on what you just read, there wasn't mention of requirement for dissents to be in Final Report?

59:40
This Addendum publication has a consensus designation so we have the right to submit a dissenting opinion

01:00:42
hey, I’d like to form a small group that will promote the idea of ending this EPDP next week

01:00:55
The Addendum does not have a consensus designation. It states preliminary conclusion.

01:01:07
Please note the Addendum states: At the time of publication of this addendum, no formal consensus call has been taken on these responses and preliminary recommendations; however, this addendum to the Initial Report did receive the support of the EPDP Team for publication for public comment.

01:01:49
+1 Berry and Caitlin. I am at a loss to understand why this insistence on a dissent in an initial report when they will have every chance to express their dissent later

01:03:39
@Berry @Caitlin: +1. On that basis, the NCSG agreed to have its minority statement on purpose 2 removed from the initial report.

01:03:47
As Marc is pointing out right now. :-)

01:03:50
+1 Berry and Caitlin. I am at a loss to understand why this insistence on a dissent in an initial report when they will have every chance to express their dissent later

01:03:57
I am afraid I have to leave, could you please promote David Cake to my spot as a panelist.

01:04:02
Tactics, Milton. It gives them the opportunity to dominate the discussion in the public comments as their opinion will be presented in the most breadth

01:04:04
@Marc: +1

01:04:27
There was this whole discussion about “narratives” on Tuesday, and we reached the conclusions Marc just reminded us of.

01:04:34
@Stephanie, we have adjusted David to member for rest of meeting.

01:05:57
There is no consensus decision though. There is a lack of a decision

01:06:11
this is a waste of time. Be adults and accept the fact that you don’t have support for your position

01:06:14
@AlanG: That was not my understanding. NCSG was the only group objecting to the draft recommendation on purpose 2, and we agreed to have our dissenting statement removed pending the publication of the final report.

01:07:22
NCSG was NOT the only group that didn’t like Purpose 2. Others were just willing to move ahead. Wish ALAC and IPC/BC would show the same maturity

01:08:32
@Laureen: LOL

01:10:00
thank you for the constructive suggestion, Laureen

01:10:43
That seems fine Laureen

01:11:31
I'm fine with Laureen's proposed edit.

01:11:37
I’m good with Laureen’s proposal too. Suggests potential options, but commits to nothing specific, which I believe is appropriate at this point.

01:12:48
indeed, the SSAD is what we are supposed to be completing

01:12:57
Janis+1

01:13:13
@Janis: I’m fine with closing this conversation…, permanently. ;-)

01:13:29
Amen Amr!

01:13:30
Yes, Hadia, you are right.

01:13:36
Hadia is correct…that is from Phase 1 of our work

01:13:38
@ Milton -- I understand your point. I think there is a modest hope that that a small group may be able to make progress on the Natural/Legal issues-- progress that might achieve consensus. If not, then of course, the issue will remain unresolved.

01:13:54
And that compromise was able to get a consensus in phase 1. Best tell your ALAC colleagues not to mess with it

01:14:11
Always so plucky Milton.

01:15:35
oh come on, Margie.

01:15:37
But it has been considered

01:15:44
No

01:15:49
Just not the way you wanted

01:17:10
exactly, let’s just move on

01:17:45
I need more coffee

01:17:53
@Janis: +1

01:18:00
If we are to include our diverging opinions, I request a postponement of one corona confinement (two weeks) to craft ours

01:18:37
YES

01:18:44
@Janis: Please!!

01:18:56
Yes, that’s a Laureen laugh :-)

01:19:09
Have to keep a sense of humor -- my primary survival tactic.

01:20:19
Indeed, Laureen

01:20:35
+1 Margie

01:20:42
@Laureen: Personally, I’d rather you stay unmuted. Have been enjoying it so far. :-)

01:23:19
Unless wasting our time on this is the objective

01:24:46
was it not reviewed by the legal committee?

01:25:04
that's better - thanks

01:25:06
There is also a Phase I memo on Legal Natural . . . are we omitting that?

01:25:23
@Milton: +1

01:25:44
that's fine

01:25:48
I wouldn't object to that actually, Milton

01:25:55
How can policy issues NOT be influenced by legal opinions!

01:25:59
That's fine

01:26:29
For clarity and accuracy, this Conclusion should start, "While legal advice indicates that Registrant Data for legal persons may be published..."

01:26:33
Alan: Just because something is legally possible does not mean it is good policy

01:26:43
@Volker: +1

01:26:59
@Volker, sure, but that is not what was said.

01:27:10
I said that

01:27:18
@AlanG: That’s exactly what we’ve been saying!!

01:28:02
The people who wrote the law think it is for the best to make this distinction.

01:28:20
Our definitions of "good policy" obviously differ.

01:28:48
I need to depart the call now and Sarah Wyld will be taking over for me…thanks Sarah!

01:28:54
Thanks Matt

01:28:55
@Hadia: The people who wrote the law have been discussing gTLD registration data policies, and have opinions on them?!

01:29:44
@AlanG: +1 on your last statement in the chat. :-)

01:30:36
The edits were to remove "also" and change "MAY" to "may", right?

01:31:00
I don’t get the difference between “may” and “MAY”.

01:31:27
Amr - I think i'ts because we're not setting out a requirement (it may do this thing) but just explaining that this thing might happen

01:31:36
(so it's lower-case)

01:32:49
+1 Sarah

01:32:57
+1 Sarah

01:33:07
Apologies I need to be in another meeting

01:34:17
yes - thank you Marc

01:34:51
yes

01:34:58
im ok

01:36:33
I can highlight that as part of my prezo.

01:38:32
The comment period ends May 5th

01:45:33
Excel FTW!

01:45:45
heck yeah

01:46:13
Oh I am nerding out on this hard. How cool

01:47:49
@MarkSV: LOL

01:48:57
Hope that we will be able to review the summaries in a format that is large enough to see (for the over 40 set). Excel is great for organizing but not very easy to read.

01:49:09
Hermes has too much time on their hands

01:53:39
Am having some connectivity issues. Will rejoin in a couple of minutes.

01:55:57
Kudos staff great work!

01:58:57
indeed

01:59:02
3 hours is doable, but perhaps we can build in a 10-minute break for human needs

01:59:07
fantastic job, Berry

01:59:12
+1 to breaks halfway through if we do a 3 hour meeting

01:59:13
big thank you to staff

01:59:48
+1 Brian on both points

01:59:55
our staff support team rocks!

02:01:02
$4.99 https://www.name.com/domain/search/icannstaff.rocks

02:01:24
@Margie: We can certainly try to do that, whenever possible, but there might be broader SG concerns we might not be able to address until they are submitted.

02:02:13
thanks Amp!

02:02:16
amr

02:03:18
Great Work thanks

02:04:40
@AlanW: +1 on all counts.

02:06:17
@MarkSV: That’s fair.

02:07:30
Glad to be reasonable in light of the unprecedented coronavirus, and grateful to our colleagues who continue to work hard to come to consensus

02:13:39
On the third bullet, if it’s simply a review of implementation, can’t a GNSO Guidance Process (GGP) serve as an acceptable mechanism?

02:19:01
haha, AlanG, you make a good impersonation of me :-)

02:19:22
i thought I had a subscription to making that point

02:19:27
AlanG: Agree completely, but am concerned that to do this, we’ll need an additional year!!

02:19:47
And in both instances …. the CPH continues to have liability ……

02:19:59
No Alan, afraid not how it works

02:20:30
you can allocate funtional responsibilities!

02:20:47
Thomas +1

02:21:18
Although there remains some ambiguity in this particular case in AlanW's defense

02:21:47
Absolutely - but the liability will follow where as a Joint controller, we are not sure that such a functional responsibility his being carried out in a proper, legal manner -

02:21:57
and yes, the CPs are still liable, but we can work on a schedule of responsibilities between ICANN and the CPs

02:22:00
@Thomas, to be clear, if the agreement allocated responsibility, does that also imply liabilities in the case of incorrect decisions?

02:22:31
@AlanW, that is the point of ambiguity. That is not established fact

02:22:51
And therefore ………….

02:23:44
I think at tTHIS point, we have to assume there will be CP liability and they need to be "comfortable" with additional automation.

02:24:02
If we are creating a policy, and removing the ability of contracted parties to control our own liability - surely that ambiguity is exactly why we have to ensure we retain that control … no?

02:24:14
Well said Alan W.

02:24:26
you can have an internal arrangement on holding harmless the party that suffered from another parties’ wrongdoing. we should have insurance / a risk fund for that

02:24:40
Just saying, it is not established fact. It may be prudent for you to protect yourself against the worst case, but we should not state unequivocally that it is a known fact at this time

02:24:41
ah. that was in response to alan g

02:26:19
And I agree with you on that Thomas - but we are also trying to create a system that is built on Data Subject Rights and not just the protection of the CPH coffers (yes that is an important aspect for us) but we must ensure that our approach is not just circumventing the true focus here - the registrant’s rights (be they legal or policy)

02:26:45
@AlanW: THANK YOU!!

02:30:53
I need to drop on the hour all.

02:31:09
@Margie: Honestly…, I think that model was not a good one at all. Lots of aspects of the new gTLD Program that qualify as policy development were done outside of proper processes. I would not think this is something we should be recommending.

02:31:11
+1 Thomas

02:31:51
@Amr and @Margie, hence why the Policy & Implementation group was formed that created things like this EPDP and the GGP.

02:32:03
@Berry: Exactly!!

02:32:17
Have to leave for another meeting, thanks all and stay well

02:32:18
I object to the representation that all CPs are competent deciders and have best interest of data subject in mind and that all requestors are incompetent and/or will disregard data subject rights. That seems to be the assumption that whenever "data subject rights" are put forward as a reason to reject various practical solutions which seem to be allowed under the regulation.

02:32:31
+1 MarkSv

02:32:41
+1 MarkSV

02:32:47
Mark - if you ave a problem with that .. .then you need to rewrite data protection law.

02:32:48
7. Wrap and confirm next EPDP Team meeting (5 minutes):a) Tuesday 31 March at 14.00 UTC. Topics to be addressed: Continued discussion of mechanism for the evolution of SSAD, reporting requirements.b) Confirm action itemsc) Confirm questions for ICANN Org, if any

02:33:02
Not true.

02:33:16
We might not be ‘competent’ - but it is our legal obligation.

02:33:53
Also lets not make policy that assumes breach ….

02:33:55
That remains to be determined

02:34:10
Thanks all

02:34:16
Thanks, all

02:34:27
Thank you all and bye

02:34:34
Thanks all. Bye.

02:34:43
Thanks