<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Title content=""><meta name=Keywords content=""><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:PMingLiU;
panose-1:2 2 5 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body bgcolor=white lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Yes, Steve.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As soon as your told me this morning, I alerted Legal and other to re-check things.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I will follow up on an answer with them.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Regards, David<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt'>David A. Olive<br>Senior Vice President<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt'>Policy Development Support<br>Managing Director<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt'>ICANN Regional Office –Istanbul</span><span style='font-size:9.0pt;font-family:"PMingLiU",serif'><br></span><span style='font-size:9.0pt'>Internet Corporation for Assigned Names and Numbers (ICANN)</span><span style='font-size:9.0pt;font-family:"PMingLiU",serif'><br><br></span><span style='font-size:9.0pt'>Direct Line: <a href="tel:+90.212.999.6212">+90.212.999.6212</a><br>Mobile: <a href="tel:+%201.%20202.341.3611">+ 1. 202.341.3611</a><br>Mobile: <a href="tel:+90.533.341.6550">+90.533.341.6550</a><o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:12.0pt;color:black'>From: </span></b><span style='font-size:12.0pt;color:black'>Stephen Deerhake <sdeerhake@nic.as><br><b>Organization: </b>AS Domain Registry<br><b>Reply-To: </b>"sdeerhake@nic.as" <sdeerhake@nic.as><br><b>Date: </b>Sunday, June 25, 2017 at 4:00 PM<br><b>To: </b>Bart Boswinkel <bart.boswinkel@icann.org>, David Olive <david.olive@icann.org><br><b>Cc: </b>"ecadmin@icann.org" <ecadmin@icann.org>, Katrina Sataki <katrina@nic.lv>, Chris Disspain <chris@disspain.uk><br><b>Subject: </b>[Ext] Still waiting for a correction to the ICANN Announcement page..<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>Greetings to you both.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>I note that as of my writing this the Rejection Action Petition Announcement web page on the ICANN web site <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_announcement-2D2017-2D06-2D24-2Den&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=h7ObVMPGpAcLv72avqZ3syNYxeg9Akd-D4l9_q4cPOQ&m=Ihio2Gync0ybMSIkVAWFmpn8JQUF08PkMEamN6Ipac4&s=Jt8k9oci7nF2cSF4qU2qlyEVnXOFTEuk-Ado_Rcr4OE&e=">https://www.icann.org/news/announcement-2017-06-24-en[icann.org]</a> has yet to be corrected as per my brief conversation with you both this morning, and also per an email to the ICANN Corporate Secretary that I sent to him when I first discovered the error even earlier this morning.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>To recap: The ICANN Web page announcement states that the Rejection Action Petition Period is 28 days. THIS IS INCORRECT.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>The correct time limit for the Rejection Action Petition Period is 21 days (Annex D Section 2.2(b)) rather than 28 days.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>I believe the 28 day notion came from an incorrect reading by someone within ICANN of Article 22.4(a)(vi)(A)(2) in the case of the ICANN Budget, Article 22.4((b)(A)(2) in the case of the IANA Budget, Article 22.5(a)(vi)(A)(2) in the case of the Operating Plan, and Article 22.5(b)(A)(2) in the case of the Strategic Plan. These specific sections relate to the minimum number of days that will transpire between the initiation of a Rejection Notice Period as defined in Annex D Section 2.2(b) and when the Budget or Plan subject to the Board Rejection Notice can come into effect.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>The controlling language regarding the length of the Rejection Action Petition Period is clearly stated in Section 2.2(b) of Annex D as 21 days from the Rejection Action Board Notification Date.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>So long as this critical error remains uncorrected, ICANN is in effect miss-leading the Empowered Community with respect to their rights under the Bylaws and the specific operational requirements for exercising those rights as detailed in Annex D.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>I am not (yet) formally stating that this is intentional on ICANN’s part, but I made the seriousness of this error clear to both of you to this morning, as well as in my prior correspondence to the Corporate Secretary. I really fail to see how it takes over six hours to make a change of this importance to the ICANN Website.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>But now by not correcting (and publicizing the correction) ASAP once ICANN was notified of the error, ICANN is in effect manipulating the Rejection Action Petition Process by misleading the Empowered Community with respect to how much time they have to react to the Board’s decisions which led to the issuance of the Rejection Action Board Notices.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Please have appropriate ICANN Staff attend to this issue immediately.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Thank you.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Best Regards,<o:p></o:p></p><p class=MsoNormal>Stephen Deerhake<o:p></o:p></p><p class=MsoNormal>ccNSO Representative to the Empowered Community Administration<o:p></o:p></p><p class=MsoNormal>ccNSO Council Member<o:p></o:p></p><p class=MsoNormal>AS Domain Registry<o:p></o:p></p><p class=MsoNormal>GDNS, LLC<o:p></o:p></p><p class=MsoNormal>+1 212 334 3660<o:p></o:p></p><p class=MsoNormal>+1 212 656 1982 (fax)<o:p></o:p></p><p class=MsoNormal>+1 917 744 7313 (mobile)<o:p></o:p></p><p class=MsoNormal><a href="mailto:sdeerhake@nic.as">sdeerhake@nic.as</a><o:p></o:p></p><p class=MsoNormal><a href="mailto:sdeerhake@gdns.net">sdeerhake@gdns.net</a><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p></div></body></html>