<div dir="ltr"><p class="MsoNormal">Thanks Alan, taking into account your note, here is another suggested update.... maybe we can get this sorted by day's end (hope springs eternal). [<i>Note: the removal of "Compliance" is to allow ICANN to figure out from whom they would like such an advisory to emanate from.] </i></p><p class="MsoNormal"><br></p><p class="MsoNormal"><b>Suggested update</b>: </p><p class="MsoNormal"><br></p><p class="MsoNormal">The effective date of the gTLD Registration Data Policy shall be [February 29, 2020]. All gTLD Registry Operators and ICANN-accredited registrars will be required to comply with the gTLD Registration Data Policy as of that date.<u></u><u></u></p><p>Until such date [February 29, 2020], ICANN <b><font color="#ff0000"><strike>[Compliance]</strike></font></b> directs Contracted Parties that registries and registrars are required EITHER to comply with the <b><u>[policy resulting from]</u></b> the recommendations contained in the Final Report OR continue to implement measures consistent with the Temporary Specification (as adopted by the ICANN Board on 17 May 2018, and expired on 25 May 2019). Registries and registrars who continue to implement measures compliant with the expired Temporary Specification will not be subject to Compliance penalty specifically related to those measures until February 29, 2020.<u></u><u></u></p><p class="MsoNormal">Failure to respond within 30 days of this notice shall be considered acceptance of the terms herein will be considered acceptance.</p><p class="MsoNormal"><br></p><p class="MsoNormal"><br></p><p class="MsoNormal"><br></p><p class="MsoNormal">Kind regards,</p><p class="MsoNormal"><br></p><p class="MsoNormal">Alan </p><p class="MsoNormal"><br></p><p class="MsoNormal"><br><br></p><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><span style="font-size:12pt;font-family:Cambria,serif">Please NOTE: This electronic message, including any attachments, may include privileged, confidential and/or inside information owned by Donuts Inc. . </span><span style="font-size:12pt;font-family:Cambria,serif">Any distribution or use of this communication by anyone other than the intended recipient(s) is strictly prohibited and may be unlawful. If you are not the intended recipient, please notify the sender by replying to this message and then delete it from your system. Thank you.</span><br></div></div></div></div></div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Mar 13, 2019 at 11:21 AM Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</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>
I think that the intent of this is exactly right, and keeping it lightweight is important.<br>
<br>
The problematic part of the wording is that it implies that contracted parties can interpret the Recs on their own prior to ICANN publishing the new Consensus Policy (CP) (presumably 6 months prior to 29 Feb 2020). For the period from xx May 2019 until the
CP is published, the Temp Spec is the rule (properly phrased). After the CP is published, the new CP may apply and must apply no later than 29 Feb.<br>
<br>
Alan<br>
<br>
At 12/03/2019 12:42 AM, Elizabeth Bacon wrote:<br>
<br>
<blockquote type="cite" class="gmail-m_3957958465680017853cite">Hello Team,<br>
In Sunday?s session, ICANN noted that they feel they need a temporary policy to bridge between the expiration of the Temporary Specification and the completion of the EPDP Consensus Policy. There was some consensus in the room that the Team had anticipated
this and provided that mechanism via Recommendation 28. In addition, the idea of what a ?temporary policy? might be raised several questions and concerns. In an effort to not recreate the wheel or implement an overly heavy solution, we proposed to Dennis
that a formal notice/advisory from ICANN Compliance to Contracted Parties to operationalize the language we previously agreed for Recommendation 28 would be sufficient and appropriate.
<br>
<br>
The language is below for your review. I look forward to your thoughts before I share with Dennis.
<br>
Thanks,<br>
Beth<br>
<br>
<br>
The effective date of the gTLD Registration Data Policy shall be [February 29, 2020]. All gTLD Registry Operators and ICANN-accredited registrars will be required to comply with the gTLD Registration Data Policy as of that date.
<br>
<br>
Until such date [February 29, 2020], ICANN Compliance directs Contracted Parties that registries and registrars are required EITHER to comply with the recommendations contained in the Final Report OR continue to implement measures consistent with the Temporary
Specification (as adopted by the ICANN Board on 17 May 2018, and expired on 25 May 2019). Registries and registrars who continue to implement measures compliant with the expired Temporary Specification will not be subject to Compliance penalty specifically
related to those measures until February 29, 2020.<br>
Failure to respond within 30 days of this notice shall be considered acceptance of the terms herein will be considered acceptance.<br>
<br>
<b>Elizabeth Bacon<br>
</b>Senior Director, Policy and Privacy<i>
<br>
</i>Public Interest Registry <br>
Direct: +1 703-956-3962 | Mobile: +1 571-352-5029| <br>
<br>
Find us on <a href="http://www.pir.org/" target="_blank">www.pir.org</a> | <a href="http://www.facebook.com/pir.org" target="_blank">
Facebook</a> | <a href="http://twitter.com/PIRegistry" target="_blank">Twitter</a> | <a href="http://instagram.com/piregistry" target="_blank">
Instagram</a> |<br>
<b><i>Celebrating 15 years of operating the .org domain<br>
</i></b> <br>
<br>
_______________________________________________<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" 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>