<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Thanks for this additional input on Recommendation 13. Please forgive these observations and consider this recommendation for closing off this remaining issue. <div class=""><br class=""></div><div class="">During our meeting Thomas was given the floor to explain his edits. During that, there was the usual chat going on: first some non-substantive commentary, then a different discussion. Partially through Thomas’ intervention, I shook myself out of watching the chat to listen to Thomas, who was making a careful, studied explanation of his addition. I kicked myself (figuratively) for missing part his explanation when, in a few months, any of us would probably give a lot to have Thomas available to answer questions such as these. It made we wonder how many of us were watching the chat instead of listening. </div><div class=""><br class=""></div><div class="">Understanding Thomas point, I made the suggestion to the group that we retain it in some form (a more complete explanation of the issue) but move it down into the body of the recommendation as an item to be considered. At that point, my sense was that the team wanted to leave it first and foremost and I withdrew my suggestion to move it. </div><div class=""><br class=""></div><div class="">Having said that, I understand Ashley’s comment that we don’t have a full handle on the effect of the GDPR sections Thomas cited on out recommendations. </div><div class=""><br class=""></div><div class="">I recommend that we: </div><div class=""><ul class="MailOutline"><li class="">respectfully ask Thomas to augment the issue somewhat with a couple / few sentences. </li><li class="">move that issue to the annotation describing the recommendation with a notation that this issue be sorted out during the implementation discussion. </li></ul><div class=""><br class=""></div><div class="">Let me know what you think. </div><div class=""><br class=""></div><div class="">Best regards,</div><div class=""><br class=""></div><div class="">Kurt</div><div class=""><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class=""><br class=""></div><div class=""><div class="">
<br class="">
At 07/02/2019 03:52 PM, Heineman, Ashley wrote:<br class="">
<br class="">
<blockquote type="cite" class="cite" cite="">Thanks for this and hello colleagues,<br class="">
<br class="">
After further reflection on today’s discussion of Recommendation 12 and the new text proposed by Thomas, I believe this language should be deleted. Specifically –“ “These criteria are applicable to disclosure requests relating to civil claims. LEA requests
will be handled according to applicable laws.†<br class="">
<br class="">
While I am extremely pleased with the state of the Recommendation overall, this new insertion has not been fully considered and I believe is misplaced.
<br class="">
<br class="">
I understand and am sympathetic to Thomas’ concerns, but that being said, I believe those concerns are best addressed elsewhere. The singular intent of Recommendation 12 is to provide clarity around the process and expectations of reasonable lawful disclosure
in terms of making requests. The recommendation attempts to ensure that expectations are set for how to submit requests and in what fashion those requests will be handled once received. The Recommendation does NOT assume that disclosure will be made and,
further, it isn’t even contemplated how and on what basis a decision for disclosing (or not) will be made. Those issues are to be dealt with in Phase 2 and/or otherwise in a specific access discussion.<br class="">
<br class="">
I’m thus concerned that by explicitly limiting this recommendation to civil requests will unfairly and unnecessarily remove the benefits of process clarity for LEA.
<br class="">
<br class="">
In light of these concerns, I strongly recommend the deletion of this text. Thomas’ legitimate concerns should then be taken up and addressed in our Phase 2 work.<br class="">
<br class="">
Thanks!<br class="">
<br class="">
Ashley<br class="">
202 482 0298<br class="">
<br class="">
<b class="">From:</b> Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org" class="">gnso-epdp-team-bounces@icann.org</a>> <b class="">On Behalf Of </b>
Caitlin Tubergen<br class="">
<b class="">Sent:</b> Thursday, February 7, 2019 3:26 PM<br class="">
<b class="">To:</b> <a href="mailto:gnso-epdp-team@icann.org" class="">gnso-epdp-team@icann.org</a><br class="">
<b class="">Subject:</b> [Gnso-epdp-team] For your review: updated recommendations 10, 11, 12<br class="">
<br class="">
Dear EPDP Team:<br class="">
<br class="">
Attached, please find the updated recommendations. The updates are the result of today’s EPDP Team discussion<br class="">
<br class="">
As always, please feel free to flag any text that you believe does not represent what the Team agreed to.<br class="">
<br class="">
Best regards,<br class="">
<br class="">
Marika, Berry, and Caitlin<br class="">
<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
Gnso-epdp-team mailing list<br class="">
<a href="mailto:Gnso-epdp-team@icann.org" class="">Gnso-epdp-team@icann.org</a><br class="">
<a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" eudora="autourl" class="">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a></blockquote>
</div>
_______________________________________________<br class="">Gnso-epdp-team mailing list<br class=""><a href="mailto:Gnso-epdp-team@icann.org" class="">Gnso-epdp-team@icann.org</a><br class="">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</div></blockquote></div><br class=""></div></body></html>