<div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Matt,<br> <br>I thank you for your mail outlining concerns of the CPH.<br><br></div><div dir="ltr" class="gmail_attr">I must admit that sometimes I also have the same feeling of slow progress in our deliberations but we work as a team and need to take into account interests of all members.<br><br></div><div dir="ltr" class="gmail_attr">Let me explain further course of actions that may alleviate (at least partially) your concerns. From the very beginning of Team's deliberations I asked the staff to capture and put aside all elements that as a result of our discussions could become part of the policy recommendations. Staff is doing this work and it will be presented to the Team in form of Zero draft either 30 August or 2 September. That will give the Team sufficient time to prepare for consideration of the Zero draft at the LA meeting.<br> <br>The structure of the draft will reflect the structure of our deliberations. On the demand side - building blocs representing request elements (requester and their categories; legal basis options; request submission modalities; applicable safeguards; possible accreditation options just to name some). On the supply side - elements representing disclosure modalities (evaluation and response modalities; possible automation; applicable safeguards just to name some). And elements of interface between demand and supply side - gateway or gateways options; liability issues, controller etc).<br><br></div><div dir="ltr" class="gmail_attr">Basically - hamburger (since ICANN lately is in gastronomic tittles:-) ).<br><br></div><div dir="ltr" class="gmail_attr">Outstanding issues (P2) should be added to building blocks where these are relevant to SSAD and we would need to find the best way of doing it.<br><br></div><div dir="ltr" class="gmail_attr">I hope that Zero draft will be accepted by the Team as a basis for further work and we will concentrate further to policy recommendation formulations.<br><br></div><div dir="ltr" class="gmail_attr">Happy to receive your reaction.<br><br></div><div dir="ltr" class="gmail_attr">Best regards<br>JK</div><div dir="ltr" class="gmail_attr"><br></div><div dir="ltr" class="gmail_attr"><br></div><div dir="ltr" class="gmail_attr">On Tue, Aug 13, 2019 at 9:25 PM Matt Serlin <<a href="mailto:matt@brandsight.com">matt@brandsight.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div class="gmail-m_-3897647994886843250WordSection1">
<p style="background:white"><span style="font-size:10pt;font-family:ArialMT,serif;color:black">Please note the below is being sent on behalf of the CPH (RrSG and RySG) reps…thank you.</span><span style="font-size:10pt;font-family:ArialMT,serif"><u></u><u></u></span></p>
<p style="background:white"><span style="font-size:10pt;font-family:ArialMT,serif;color:black">With less than four weeks until our face-to-face meeting, the CPH is increasingly concerned with the lack of meaningful progress towards a first draft of policy
recommendations. We attribute this lack of movement in part to the shortcomings of our approach to evaluating use cases. In our view, the success of this exercise depends on EPDP team members producing focused and specific use cases that, when viewed together,
illustrate procedural commonalities and insights necessary to inform our recommendations. Instead, the use cases and our discussions so far are so broad or generalized that it is no longer clear how our review will ultimately lead to policy recommendation
or actionable outcomes. Without an immediate correction to refocus our efforts, we are concerned about the EPDP team’s ability to meet deadlines and ultimately succeed in delivering a timely Initial Report for Phase II.
</span><span style="font-size:10pt"><u></u><u></u></span></p>
<p style="background:white"><span style="font-size:10pt;font-family:ArialMT,serif;color:black">The CPH proposes the following reasonable steps to help improve the utility of the use cases and the efficiency of our deliberations:
</span><span style="font-size:10pt"><u></u><u></u></span></p>
<ul type="disc">
<li style="background:white"><span style="font-size:10pt;font-family:ArialMT,serif;color:black">● Use cases must be more specific, detailed, and focused on procedure in order to help us make observations and reach agreement. Use
cases should be illustrative of a discrete set of procedural, legal, and policy considerations, rather than focused on validating a broad range of outcomes.
</span><span style="font-size:10pt"><u></u><u></u></span></li><li style="background:white"><span style="font-size:10pt;font-family:ArialMT,serif;color:black">● Our approach should not only consider use cases where access/disclosure is appropriate, but also examine circumstances where access/disclosure
would not be granted. Our analysis of use cases is not intended to make value judgments about “deserving” users or interests. Our policy must focus on what is compliant, not what is merely desired.
</span><span style="font-size:10pt"><u></u><u></u></span></li><li style="background:white"><span style="font-size:10pt;font-family:ArialMT,serif;color:black">● We must prioritize and document agreement as we proceed through each use case. The Next Gen RDS implemented a “tentative agreements”
document maintained by ICANN Staff to capture a list of non-binding, informal agreements that the group built upon as deliberations progressed. The document served as a transparent reference for all parties to help avoid re-litigating issues. This approach
would also help solve a significant pain point from Phase I where the CPH found it difficult to track the source of agreements that ended up in the draft recommendations. We recommend adopting the same procedure.
</span><span style="font-size:10pt"><u></u><u></u></span></li></ul>
<p style="margin-left:0.5in;background:white"><span style="font-size:10pt;font-family:ArialMT,serif;color:black">The CPH remains committed to the success of the EPDP and offers these suggestions in the spirit of achieving our shared goal of timely completion
of a Final Report for Phase II. </span><span style="font-size:10pt"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10pt"><u></u> <u></u></span></p>
</div>
</div>
_______________________________________________<br>
Gnso-epdp-team mailing list<br>
<a href="mailto:Gnso-epdp-team@icann.org" target="_blank">Gnso-epdp-team@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a><br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</blockquote></div></div>