<html xmlns:v="urn:schemas-microsoft-com:vml" 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 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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:black">Dear IOT members, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">In follow up to ICANN org’s pending action item to draft proposed revisions to Rule 4: Time for Filing to provide a proposed “release valve” for late filings, we are presenting the attached draft for the IOT’s
consideration. As anticipated, this draft retains the 120 days deadline and notes that the current 12 month outer deadline for filing is under discussion. In addition, the proposed revisions also provide the criteria under which a party may file a statement
of a dispute after the deadline to file has expire, including allowances for when the claimant could not have been aware earlier, or in situations where extraordinary circumstances beyond the control of the claimant kept it from filing in a timely manner.
The proposed revision also includes an external limit of four years from the date of action for all filings. ICANN org proposes this, as experience has documented that outcomes of IRPs could impact contracts, and there is a four year statute of limitations
on breach of contract claims within California. Limiting the ability to file an IRP within that window still provides more time for being able to hold ICANN accountable, even in extraordinary circumstances, while balancing against statutory limitations that
could be impacted. We are also attaching a redline comparison of the proposed revisions to the current Rule 4. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">We look forward to discussing this on today’s call.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Best regards, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Liz <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">----<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Elizabeth D. Le<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Associate General Counsel | ICANN<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">12025 Waterfront Drive, Suite 300<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Los Angeles, CA 90094<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><a href="mailto:elizabeth.le@icann.org">elizabeth.le@icann.org</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>