<div dir="ltr">Thank you for the clarification Francisco.<div><br></div><div>Cheers,</div><div><br></div><div>Ben</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 21, 2016 at 1:06 PM, Francisco Arias <span dir="ltr"><<a href="mailto:francisco.arias@icann.org" target="_blank">francisco.arias@icann.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear colleagues,<br>
<br>
Apologies for the confusion caused, I wrote "do not implement before" when I meant "do not deploy before" date. In other words, we are proposing to have a date for when this new functionality can be turned on. Contracted parties can, of course, start implementation/development at their convenience. ICANN’s objective for the do not deploy before date is to allow ICANN’s tools to be updated to account for the changes required by CL&D, thus preventing our tools from generating false non-conformance reports during testing and/or monitoring.<br>
<br>
After discussing this internally, we think we only need this date for the CL&D policy and not for RDAP. As a reminder, the CL&D policy only applies to registries.<br>
<br>
In summary, we are proposing to have a "do not deploy before" date for the CL&D policy that only applies to registries.<br>
<br>
Regards,<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Francisco<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On 7/13/16, 6:23 PM, "Michele Neylon - Blacknight" <<a href="mailto:michele@blacknight.com">michele@blacknight.com</a>> wrote:<br>
<br>
This is contrary to how changes are normally implemented and I suspect quite a few of us would have issues with this.<br>
These kind of changes are of zero benefit to registrars and are only implemented as a contractual obligation. Imposing further restrictions on when we can implement them has a non-zero impact on us, so I would oppose this<br>
<br>
Regards<br>
<br>
Michele<br>
<br>
Mr Michele Neylon<br>
Blacknight Hosting & Domains<br>
<a href="http://www.blacknight.host/" rel="noreferrer" target="_blank">http://www.blacknight.host/</a><br>
<a href="http://www.mneylon.social" rel="noreferrer" target="_blank">http://www.mneylon.social</a><br>
Sent from mobile so typos and brevity are normal<br>
<br>
> On 13 Jul 2016, at 21:20, Francisco Arias <<a href="mailto:francisco.arias@icann.org">francisco.arias@icann.org</a>> wrote:<br>
><br>
> Dear colleagues,<br>
><br>
> As you may recall the gTLD RDAP profile and Thick Whois policy implementation – Consistent Labeling and Display (CL&D for short) are synchronized and have a proposed effective date of 1 February 2017. This means enforcement would start on that date. However, in monitoring compliance with a given policy or contractual requirement we also need time to develop our tools and be able to *not* report false compliance issues (e.g., our current tool would raise an issue if it encounters the new Whois output that is specified in CL&D). We need to update that tool to avoid that issue from happening.<br>
><br>
> We’d like to add to both CL&D and the RDAP profile a “do not implement before” date to avoid the aforementioned issue. We are thinking we are going to need approximately four months to update/build our tools be able to identify the updated Whois output and RDAP output. That would give contracted parties approximately a two-month window for release before the effective. We are planning to add such a date to the documents, unless there is a reason why people think we should not.<br>
><br>
> Regards,<br>
><br>
> --<br>
> Francisco<br>
><br>
><br>
><br>
><br>
><br>
<br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><h4 style="margin:0px;padding:0px;font-family:Arial,sans-serif;color:rgb(148,157,158);font-weight:normal;line-height:17px">Benoit Levac<br>VP Engineering, Registry Platform</h4><a href="http://www.rightside.co/" style="color:rgb(148,157,158);text-decoration:none;font-family:'Times New Roman';font-size:medium" target="_blank"><img src="http://madebygraphiti.com/rightside/signature/rightside_logo.png" alt="Rightside" style="display:block;margin:20px 0px"></a><span style="color:rgb(0,0,0);font-family:'Times New Roman';font-size:medium"></span><h5 style="margin:0px;padding:0px;font-size:13px;font-family:Arial,sans-serif;color:rgb(148,157,158);font-weight:normal;line-height:17px"><strong>Office</strong> | 425-298-2337<br><strong>Mobile</strong> | 613-617-4416</h5><p style="margin:5px 0px 0px;padding:0px;font-family:Arial,sans-serif;color:rgb(148,157,158);line-height:19px"><a href="mailto:benoit.levac@rightside.co" target="_blank">benoit.levac@rightside.co</a><br><a href="http://www.rightside.co" target="_blank">www.rightside.co</a></p></div></div>
</div></div>