<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Thank you very much for this work. I guess you mean to mark the concerns by 4th Feb and not March. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Here are some of my comments: </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><i>Line 1542, Rec 12: Reasonable access should be called "parameters for ". Why does line 1542 recommends a modified version?</i></div><div class="gmail_default" style="font-family:verdana,sans-serif"><font color="#0000ff">Comment from KA</font> </div><div class="gmail_default" style="font-family:verdana,sans-serif"><font color="#0000ff">We better use the formulation agreed in Toronto in saying " as for the term "<i>Reasonable access"pending to further actions on the matter the Team proposed to use the term " parameter </i></font><i><font color="#0000ff">responding to lawful disclosure requests" on an interim basis </font></i></div><div class="gmail_default" style="font-family:verdana,sans-serif"><i>Line 1558, Rec 12: It is worrisome that so much leeway and emphasis has been given for the implementation phase to clarify the criteria further.</i></div><div class="gmail_default" style="font-family:verdana,sans-serif"><font color="#0000ff" style="">Comment from KA</font></div><div class="gmail_default" style="font-family:verdana,sans-serif"><i><font color="#0000ff">On the contrary we need to clearly describe the sequence of action as specified in Recommendation </font></i></div><div class="gmail_default" style="font-family:verdana,sans-serif"><i>Line 1580, Rec 12: When did we agree that a separate guideline/timeline might be considered for disclosure of personal data in urgent circumstances? I did record my objection to that.</i></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="color:rgb(0,0,255)">Comment from KA</span> <i><br></i></div><div class="gmail_default" style="font-family:verdana,sans-serif"><font color="#0000ff">We need to verfy what was agreed from Transcrip and record</font>. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><i>Line 1589: EPDP recommends that working on these (disclosure) criteria start as soon as possible. What does that mean? Are we recommending that implementation of disclosure criteria start sooner than anything else? </i></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="color:rgb(0,0,255)">Comment from KA</span> <br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><font color="#0000ff">No. There is not such understanding of the term " as soon as possible " meaning to establish order of priority in dealing several items or taking actions on several items </font></div><div class="gmail_default" style="font-family:verdana,sans-serif"><i>Rec 12 in general: all the "access" language has to be replaced with disclosure requests. </i></div><div class="gmail_default" style="font-family:verdana,sans-serif"><i><font color="#0000ff">Comment from Kavouss </font></i></div><div class="gmail_default" style="font-family:verdana,sans-serif"><font color="#0000ff" style="">See my comments above in stating for the time being on an interin basis such replacement is being proposed.<b>NO PERMANENT REPLACE IS ACCEPTABLE </b></font></div><div class="gmail_default" style="font-family:verdana,sans-serif"><i><br></i></div><div class="gmail_default" style="font-family:verdana,sans-serif"><i>Line 1936, Rec 13: Joint Controller Agreement language is removed, providing no rationale. Other than Chris Disspain's point of view and the US government reasoning, as I say I don't see objections to JCA. If you have considered the public comments to make this change, please let us know. If you have considered other factors I would like to know what they are. <br></i></div><div class="gmail_default" style="font-family:verdana,sans-serif">Comment from Kavouss </div><div class="gmail_default" style="font-family:verdana,sans-serif"><font color="#0000ff">This requires further debate to remove or retain to JCA</font></div><div class="gmail_default" style="font-family:verdana,sans-serif"><i><br></i></div><div class="gmail_default" style="font-family:verdana,sans-serif"><i>Line 2066, Rec 18: If we are getting rid of data processing agreement replacing with data protection arrangements (which I don't personally agree with) then please be consistent throughout the document. Or are we only getting rid of DPA and JCA only regarding registries and registrars?</i></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="color:rgb(0,0,255)">Comment from KA</span> <br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><font color="#0000ff">I agree with the question raised ?</font> <i><br></i></div><div class="gmail_default" style="font-family:verdana,sans-serif"><i>Line 2129, Rec21: Data processing agreement/ JCA mentioned for Escrows etc. Are we keeping this language?</i></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="color:rgb(0,0,255)">Comment from KA</span> </div><div class="gmail_default" style="font-family:verdana,sans-serif"><font color="#0000ff">I also agree with the question raised </font><i><br></i></div><div class="gmail_default" style="font-family:verdana,sans-serif"><font color="#0000ff">Kavouss </font></div><div class="gmail_default" style="font-family:verdana,sans-serif"><i>I will send more comments soon. </i></div><div class="gmail-yj6qo gmail-ajU" style="outline:none;padding:10px 0px;width:22px;margin:2px 0px 0px"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Feb 3, 2019 at 9:28 AM farzaneh badii <<a href="mailto:farzaneh.badii@gmail.com">farzaneh.badii@gmail.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 dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Thank you very much for this work. I guess you mean to mark the concerns by 4th Feb and not March. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Here are some of my comments: </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Line 1542, Rec 12: Reasonable access should be called "parameters for responding to lawful disclosure requests". Why does line 1542 recommends a modified version?</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Line 1558, Rec 12: It is worrisome that so much leeway and emphasis has been given for the implementation phase to clarify the criteria further.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Line 1580, Rec 12: When did we agree that a separate guideline/timeline might be considered for disclosure of personal data in urgent circumstances? I did record my objection to that.</div><div class="gmail_default" style="font-family:verdana,sans-serif">Line 1589: EPDP recommends that working on these (disclosure) criteria start as soon as possible. What does that mean? Are we recommending that implementation of disclosure criteria start sooner than anything else? </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Rec 12 in general: all the "access" language has to be replaced with disclosure requests. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Line 1936, Rec 13: Joint Controller Agreement language is removed, providing no rationale. Other than Chris Disspain's point of view and the US government reasoning, as I say I don't see objections to JCA. If you have considered the public comments to make this change, please let us know. If you have considered other factors I would like to know what they are. <br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Line 2066, Rec 18: If we are getting rid of data processing agreement replacing with data protection arrangements (which I don't personally agree with) then please be consistent throughout the document. Or are we only getting rid of DPA and JCA only regarding registries and registrars?</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Line 2129, Rec21: Data processing agreement/ JCA mentioned for Escrows etc. Are we keeping this language?</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I will send more comments soon. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div><div dir="ltr" class="gmail-m_-5276489143262766629m_607584515685925115gmail_signature"><div dir="ltr"><div><font face="verdana, sans-serif">Farzaneh </font></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 1, 2019 at 6:10 PM Marika Konings <<a href="mailto:marika.konings@icann.org" target="_blank">marika.konings@icann.org</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_-5276489143262766629gmail-m_607584515685925115gmail-m_6277579188242195286WordSection1">
<p class="MsoNormal"><span style="font-size:11pt">Dear EPDP Team,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Please find attached for your review the latest version of the Final Report. In relation to section 5, EPDP Team Responses to Charter Questions & Recommendations, please note that those sections highlighted
in green are considered finalized for inclusion in the Final Report, sections in blue are still under review / consideration (but these do include the latest language, unless indicated differently).
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">For substantive issues or concerns, please flag these on the mailing list by
<b><u>Monday 4 March COB</u></b> so that these can be included in the meeting agendas for next week. If you want to reference specific parts of the report, please use the line numbering of the attached pdf version. For any minor edits / updates, please use
the google doc: <a href="https://docs.google.com/document/d/1sVZ9odV0qK1Bk8a4bDwWe5RW_PBzOnYBhHW_GnLL8jw/edit?ts=5c4f07ef" target="_blank">
https://docs.google.com/document/d/1sVZ9odV0qK1Bk8a4bDwWe5RW_PBzOnYBhHW_GnLL8jw/edit?ts=5c4f07ef</a>. On the wiki (see
<a href="https://community.icann.org/x/VZwWBg" target="_blank">https://community.icann.org/x/VZwWBg</a>), we have also posted a Word and clean version for those of you that prefer that format.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">As you review the Final Report, we want to remind you of Kurt’s message that also seem to apply here: “study the balancing that went into this and be ready to accept wording in cases where it does not match
your own choice”. <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">As a reminder, revisions to the data elements workbooks to ensure alignment with EPDP recommendations are being undertaken by a small team which is expected to share the results of its work shortly.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Best regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Caitlin, Berry and Marika<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><i><span style="font-size:10pt;color:black">Marika Konings</span></i></b><span style="font-size:10pt;color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><i><span style="font-size:10pt;color:black">Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) </span></i><span style="font-size:10pt;color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><i><span style="font-size:10pt;color:black">Email: <a href="mailto:marika.konings@icann.org" target="_blank"><span style="color:rgb(5,99,193)">marika.konings@icann.org</span></a> </span></i><span style="font-size:10pt;color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><i><span style="font-size:10pt;color:black"> </span></i><span style="font-size:10pt;color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><i><span style="font-size:10pt;color:black">Follow the GNSO via Twitter @ICANN_GNSO</span></i><span style="font-size:10pt;color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><i><span style="font-size:10pt;color:black">Find out more about the GNSO by taking our <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses_gnso&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=5DXgId95wrCsHi--pxTiJD7bMB9r-T5ytCn7od3CF2Q&s=Cg5uQf0yAfw-qlFZ0WNBfsLmmtBNUiH0SuI6Vg-gXBQ&e=" target="_blank"><span style="color:rgb(5,99,193)">interactive
courses</span></a> and visiting the <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gnso.icann.org_files_gnso_presentations_policy-2Defforts.htm-23newcomers&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=5DXgId95wrCsHi--pxTiJD7bMB9r-T5ytCn7od3CF2Q&s=tT-E2RoAucUb3pfL9zmlbRdq1sytaEf765KOEkBVCjk&e=" target="_blank"><span style="color:rgb(5,99,193)">GNSO
Newcomer pages</span></a>. </span></i><span style="font-size:10pt;color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></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></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>