<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=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:DFKai-SB;
panose-1:3 0 5 9 0 0 0 0 0 0;}
@font-face
{font-family:"\@DFKai-SB";
panose-1:3 0 5 9 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoCommentText, li.MsoCommentText, div.MsoCommentText
{mso-style-priority:99;
mso-style-link:"Comment Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
span.MsoCommentReference
{mso-style-priority:99;}
p.MsoBlockText, li.MsoBlockText, div.MsoBlockText
{mso-style-priority:99;
mso-style-link:"Block Text Char";
margin-top:0in;
margin-right:.5in;
margin-bottom:12.0pt;
margin-left:4.3pt;
line-height:121%;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.CommentTextChar
{mso-style-name:"Comment Text Char";
mso-style-priority:99;
mso-style-link:"Comment Text";
font-family:"Times New Roman","serif";}
span.BlockTextChar
{mso-style-name:"Block Text Char";
mso-style-priority:99;
mso-style-link:"Block Text";
font-family:"Times New Roman","serif";}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
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><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Hi Becky,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">I think Avri and the others who urge this point have a decent and understandable inclination, especially given the old IRP’s limitation to procedural rather than substantive
review. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">But I wonder if we can/should take such an approach.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">First, while I don’t necessarily see retroactivity as explicitly beyond the CCWG’s remit, it seems retroactivity might either be mandated by or contrary to the new bylaws.
Here’s what I mean:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Bylaw Section 4.3(a) (speaking to what the new IRP is intended to do) is in the present tense and appears to have an exclusively prospective effect, at least in my reading.
The same is true for the definition of “Covered Actions” in Section 4.3(b)(ii) (“…actions or failures to act … that
<u>give</u> rise to a Dispute.”) (my emphasis). I think there is a fair argument here that the Bylaws preclude looking back to pre-existing claims. On the other hand, it could be that California law would require even such a prospective bylaw to have present
application and thus application to presently pending matters. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Given this, we might want to ask Rosemary about this.
<s><o:p></o:p></s></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Also, I think there is an issue of fairness involved in going back and changing substantive rules retroactively. Strictly procedural rules applied prospectively from the
date of their taking effect are another matter.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">David
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">David McAuley<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">International Policy Manager<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Verisign Inc.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">703-948-4154<span style="color:#1F497D"><o:p></o:p></span></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> iot-bounces@icann.org [mailto:iot-bounces@icann.org]
<b>On Behalf Of </b>Burr, Becky<br>
<b>Sent:</b> Monday, August 22, 2016 4:37 PM<br>
<b>To:</b> iot@icann.org<br>
<b>Subject:</b> [IOT] Discussion thread #1<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoBlockText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoBlockText"><span style="font-family:"Helvetica","sans-serif";color:black;letter-spacing:-.05pt">The current draft states:</span><span style="color:black"><o:p></o:p></span></p>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<p class="MsoBlockText"><span style="font-family:"Helvetica","sans-serif";color:black;letter-spacing:-.05pt">IRPs commenced prior to the adoption of these Updated Supplementary Procedures shall be governed by the Supplementary Procedures in effect at the time
such IRPs were commenced. </span><span style="color:black"><o:p></o:p></span></p>
</blockquote>
<p class="MsoBlockText"><span style="font-family:"Helvetica","sans-serif";color:black">In other words, if you filed an IRP before these new rules get adopted on October 1, you continue to operate under the existing supplementary rules and note the updated supplementary
rules. Several people have expressed disagreement with that principle, and Avri has suggested adding language along the lines below (I have tweaked it slightly):</span><span style="color:black"><o:p></o:p></span></p>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<p class="MsoBlockText"><span style="font-family:"Helvetica","sans-serif";color:red;letter-spacing:-.05pt">[unless
</span><span style="font-family:"Helvetica","sans-serif";color:red">the IRP Panel determines that the party requesting application of the Updated Supplementary has demonstrated
<span style="letter-spacing:-.05pt">that application of the former Supplementary Procedures would be unjust and
</span>impracticable to the requesting party and application of the Updated Supplementary Rules would not materially disadvantage any other party’s substantive rights<span style="letter-spacing:-.05pt">. Any party to a then-pending IRP may oppose the request
for application of the Updated Supplementary Procedures. </span>Requests to apply the Updated Supplementary Procedures will
<span style="letter-spacing:-.05pt">be resolved by the IRP PANEL in its discretion]</span></span><span style="color:black"><o:p></o:p></span></p>
</blockquote>
<p class="MsoBlockText"><span style="font-family:"Helvetica","sans-serif";color:black">This is a difficult and important issue. Most importantly, we need to understand and address the impact that this change would have on IRPs that are ongoing as of October
1 2016. Would a claimant be entitled to essentially re-start the process to take advantage of a changed page limitation or the updated standard of review, even if a hearing has taken place and the only remaining step is for the Panel to issue a declaration?
What about those who are close to the end of the process and want to go back and move to have an in person hearing? Could this be limited in some way? </span><span class="MsoCommentReference"><span style="font-size:8.0pt;line-height:121%;font-family:"Helvetica","sans-serif";color:black">ICANN
thinks that </span></span><span style="font-family:"Helvetica","sans-serif";color:black">needs to be a bright line between IRPs filed under the old Bylaws/old procedures, and the IRPs filed under the new Bylaws/new procedures. </span><span style="color:black"><o:p></o:p></span></p>
<div>
<div>
<div id="_com_1">
<p class="MsoCommentText"><span style="font-size:12.0pt;font-family:"Helvetica","sans-serif";color:black">Also, since this is retroactive and would impact IRPs filed under the old rules, query whether this is within the scope of our remit.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoCommentText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoCommentText"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoCommentText"><span style="font-size:12.0pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal" style="margin-top:12.0pt"><b><span style="font-size:9.0pt;color:black">J. Beckwith Burr</span></b><b><span style="font-size:10.0pt;color:#262626">
</span></b><b><span style="font-size:9.0pt;color:#3366FF"><br>
</span></b><b><span style="font-size:9.0pt;color:#008656">Neustar, Inc.</span></b><b><span style="font-size:9.0pt;color:#068658">
</span></b><span style="font-size:9.0pt;color:#7D7D7D">/</span><b><span style="font-size:9.0pt;color:#068658">
</span></b><span style="font-size:9.0pt;color:#7D7D7D">Deputy General Counsel & Chief Privacy Officer<br>
1775 Pennsylvania Avenue NW, Washington D.C. 20006</span><span style="font-size:9.0pt;color:gray"><br>
</span><b><span style="font-size:9.0pt;color:#008656">Office:</span></b><b><span style="font-size:9.0pt;color:#7D7D7D">
</span></b><span style="font-size:9.0pt;color:#7D7D7D">+1.202.533.2932 </span><b><span style="font-size:9.0pt;color:#008656">Mobile:</span></b><b><span style="font-size:9.0pt;color:#7D7D7D">
</span></b><span style="font-size:9.0pt;color:#7D7D7D">+1.202.352.6367 </span><strong><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#7D7D7D">/</span></strong><span style="font-size:9.0pt;color:#068658">
</span><span style="color:black"><a href="http://www.neustar.biz"><b><span style="font-size:9.0pt;color:#008656">neustar.biz</span></b></a><o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>