<div dir="ltr"><div dir="ltr">Thanks Sarah. <div><br></div><div>Looking forward to discussing this further on the call tomorrow. In the mean time here are my thoughts inline....</div></div><br><div class="gmail_quote"><div dir="ltr" class="m_-6116649378849360016gmail_attr">On Mon, Jan 28, 2019 at 12:23 PM Sarah Wyld <<a href="mailto:swyld@tucows.com" target="_blank">swyld@tucows.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 bgcolor="#FFFFFF">
<p><font size="-1"><font face="Verdana">Dear EPDP Team,</font></font></p>
<p><font size="-1"><font face="Verdana">Thanks to all those who
worked on the updated Rec 12, especially Alex Deacon, it was
good to be able to work from your thoughtful updates. I have
attached a revised version of this Recommendation, however I'm
not sure that my tracked changes were successful, here's
hoping. <br></font></font></p></div></blockquote><div>[Alex] they made it thru!</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><p><font size="-1"><font face="Verdana">
</font></font></p>
<p><font size="-1"><font face="Verdana">The RrSG supports the
proposed ""Format by which requests should be made and
responses are provided"", as well as the requirement for the
CP to publish information on their website about how to make a
disclosure request. <br>
<br>
It is unclear exactly which text in the Temp. Spec. is to be
updated with the phrase ""requests for lawful disclosure.”
This may be acceptable, if it is limited to the title of the
section; otherwise it would be appreciated if this could be
clarified. <br></font></font></p></div></blockquote><div><br></div><div>[Alex ] Agree some clarity is needed here. If we are not going to "redline" the temp spec, then any policy we agree to needs to be explicit in the final report (vs. some promise to update the temp spec). </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><p><font size="-1"><font face="Verdana">
<br>
The RrSG does not support a requirement to include a link to
this process in any RDS response, as this may conflict with
the CL&D Policy or the RDAP Profile which remains in
progress with the RDAP WG. <br></font></font></p></div></blockquote><div><br></div><div>[Alex] I don't believe this would conflict with the CL&D policy. What I had in mind is to also add instructions in "RDS" outputs where there is a freeform text section at the end of the response. See for example the output from <a href="http://whois.donuts.co" target="_blank">whois.donuts.co</a> attached - I've highlighted the relevant text. This seems helpful IMO. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><p><font size="-1"><font face="Verdana">
<br>
The RrSG notes that the specific legal basis for disclosure
may play a role in determining what information should be
included in the disclosure request, so this can be the minimum
set but it may not work for all scenarios. That said, the
proposed set of information required in the request is
appropriate. <br></font></font></p></div></blockquote><div>[Alex] Agree. My focus when drafting this was on 6.1.f disclosure, but clearly if a reasonable disclosure request comes from LEA then things are different. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><p><font size="-1"><font face="Verdana">
<br>
Regarding the timelines for responses, the RrSG would support
the second version of the text: "Contracted Parties must
acknowledge receipt of a Reasonable Disclosure Request without
unreasonable delay, but ordinarily not more than 2 business
days from receipt." <br></font></font></p></div></blockquote><div>[Alex] Thanks - I think this can be further refined. perhaps along the lines of "with response within 2 days unless circumstances can be shown that this time frame is not possible." </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><p><font size="-1"><font face="Verdana">
<br>
If a timeline for processing and responding to the disclosure
requests must be defined in this EPDP, it should be 30 days,
in order to align with the Art. 12 GDPR timeframe for
providing information to the data subject.<br></font></font></p></div></blockquote><div><br></div><div>[Alex] Article 12 seems to be specific to transparency requirements as they relate to the rights of the data subject, so it iss not clear if it applies here. In either case as long as the variable "Y" is "reasonable" we would be OK with that. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><p><font size="-1"><font face="Verdana">
<br>
Finally, regarding the proposed four types of responses to a
disclosure request, requiring specific information to be
included in the response is too detailed. We should expect the
CP to provide a reasonably detailed response, including the
info that the Controller determines should be disclosed.
Blanket denials must be permitted where justified, with the
decision made by the CP. <br></font></font></p></div></blockquote><div>[Alex] Lets discuss this further on the call today. To enable predictability I think it is important to have some high level recommendations regarding responses here. </div><div><br></div><div>Finally, I note in the first paragraph you deleted the phrase "notwithstanding discussions related to.....". If you recall in Toronto we discussed the need for a "reasonable access/disclosure" process to live in parallel with any future UAM regime to accomodate requestors (on an ad hoc basis) who may not be accredited. i.e. Rec 12 should neither wait for, nor be replaced by, a future UAM. </div><div><br></div><div>Thanks. </div><div>Alex</div><div><br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><p><font size="-1"><font face="Verdana">
</font></font></p>
<p><font size="-1"><font face="Verdana">Thank you,</font></font><br>
</p>
<pre class="m_-6116649378849360016gmail-m_3103791965352170590moz-signature" cols="72">--
Sarah Wyld
Domains Product Team
Tucows
<span id="m_-6116649378849360016gc-number-675" class="m_-6116649378849360016gc-cs-link" title="Call with Google Voice"><span id="gc-number-725" class="gc-cs-link" title="Call with Google Voice">+1.416 535 0123</span></span> Ext. 1392
</pre>
<div class="m_-6116649378849360016gmail-m_3103791965352170590moz-cite-prefix">On 1/28/2019 10:02 AM, Marika Konings
wrote:<br>
</div>
<blockquote type="cite">
<div class="m_-6116649378849360016gmail-m_3103791965352170590WordSection1">
<p class="MsoNormal">Dear EPDP Team,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Recommendation #12 and the proposed
language by the small team are on the agenda for tomorrow’s
EPDP Team meeting. To facilitate that discussion, please share
your groups thoughts, concerns and/or proposed changes with
the mailing list ahead of tomorrow’s meeting. Please focus on
those aspects that could affect your group’s support for this
recommendation.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thanks,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Caitlin, Berry and Marika<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12pt;color:black">From: </span></b><span style="font-size:12pt;color:black">Gnso-epdp-team
<a class="m_-6116649378849360016gmail-m_3103791965352170590moz-txt-link-rfc2396E" href="mailto:gnso-epdp-team-bounces@icann.org" target="_blank"><gnso-epdp-team-bounces@icann.org></a> on behalf of Alex
Deacon <a class="m_-6116649378849360016gmail-m_3103791965352170590moz-txt-link-rfc2396E" href="mailto:alex@colevalleyconsulting.com" target="_blank"><alex@colevalleyconsulting.com></a><br>
<b>Date: </b>Friday, January 25, 2019 at 11:59<br>
<b>To: </b>EPDP <a class="m_-6116649378849360016gmail-m_3103791965352170590moz-txt-link-rfc2396E" href="mailto:gnso-epdp-team@icann.org" target="_blank"><gnso-epdp-team@icann.org></a><br>
<b>Subject: </b>[Gnso-epdp-team] Recommendation 12<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">All, <u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">At the very end of our face to face a
very small team (tiny team?) met to discuss updates to
Recommendation 12 (reasonable access). The redline
attached is where we ended up. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Alex<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"> <br clear="all">
<u></u><u></u></p>
<div>
<div>
<div>
<p class="MsoNormal">___________ <u></u><u></u></p>
<div>
<p class="MsoNormal"><b>Alex Deacon</b><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Cole Valley Consulting<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><a href="mailto:alex@colevalleyconsulting.com" target="_blank">alex@colevalleyconsulting.com</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span class="m_-6116649378849360016gmail-m_3103791965352170590gc-cs-link"><span id="m_-6116649378849360016gc-number-676" class="m_-6116649378849360016gc-cs-link" title="Call with Google Voice"><span id="gc-number-726" class="gc-cs-link" title="Call with Google Voice">+1.415.488.6009</span></span></span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="m_-6116649378849360016gmail-m_3103791965352170590mimeAttachmentHeader"></fieldset>
<pre class="m_-6116649378849360016gmail-m_3103791965352170590moz-quote-pre">_______________________________________________
Gnso-epdp-team mailing list
<a class="m_-6116649378849360016gmail-m_3103791965352170590moz-txt-link-abbreviated" href="mailto:Gnso-epdp-team@icann.org" target="_blank">Gnso-epdp-team@icann.org</a>
<a class="m_-6116649378849360016gmail-m_3103791965352170590moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a></pre>
</blockquote>
</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></blockquote></div></div>