<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 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;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
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;}
/* List Definitions */
@list l0
{mso-list-id:778838663;
mso-list-type:hybrid;
mso-list-template-ids:-2134471946 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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">Dear members of the IRP IOT,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">On tomorrow’s agenda is an item described as “5. Attempt to segment out some issues for early decision”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I am going to ask that we consider a list (see below) of certain comments that may lend themselves to quick resolution, at least in discrete parts in some cases.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Here are the comments I refer to and my thinking on them:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoListParagraphCxSpFirst" style="margin-bottom:10.0pt;mso-add-space:auto;text-indent:-.25in;line-height:115%;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif">ALAC – a
<a href="https://forum.icann.org/lists/comments-irp-supp-procedures-28nov16/pdfr73b8iz2zV.pdf">
comment</a> about continuous IRP improvement. I note that there is provision to allow for review of IRP at Bylaw 4.6(b)(ii)(F) and that, in my opinion, should be sufficient.<o:p></o:p></span></p>
<p class="MsoListParagraphCxSpMiddle" style="margin-bottom:10.0pt;mso-add-space:auto;line-height:115%">
<span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoListParagraphCxSpMiddle" style="margin-bottom:10.0pt;mso-add-space:auto;text-indent:-.25in;line-height:115%;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif">Some of IPC
<a href="https://forum.icann.org/lists/comments-irp-supp-procedures-28nov16/pdft75S74tOev.pdf">
comments</a> – regarding invoice date, panel make-up on appeals, and wording about ICDR rules themselves not be overtaken as regards appeals, and costs of delay on appeal. In my opinion the invoice date as the date to measure when costs are due would be fine;
I think the appeals panel should be left as is in current bylaw and am not sure it would be fair to eliminate the judges who ruled below; a rule specifically calling out an underlying ICDR rule seems a bad idea to me as that underlying rule could change; and
costs of delays on appeals can be handled by panel as matter of discretion. <o:p>
</o:p></span></p>
<p class="MsoListParagraphCxSpMiddle" style="margin-bottom:10.0pt;mso-add-space:auto;line-height:115%">
<span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoListParagraphCxSpMiddle" style="margin-bottom:10.0pt;mso-add-space:auto;text-indent:-.25in;line-height:115%;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif"><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif">DotMusic – These
<a href="https://forum.icann.org/lists/comments-irp-supp-procedures-28nov16/pdfzqApbhRMhH.pdf">
comments</a> seek to eliminate Board confirmation of standing panelists nominated by SOs and ACs. But that confirmation process is in the bylaws and we cannot overturn that.<o:p></o:p></span></p>
<p class="MsoListParagraphCxSpMiddle" style="margin-bottom:10.0pt;mso-add-space:auto;line-height:115%">
<span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoListParagraphCxSpMiddle" style="margin-bottom:10.0pt;mso-add-space:auto;text-indent:-.25in;line-height:115%;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif"><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif">DotRegistry – This
<a href="https://forum.icann.org/lists/comments-irp-supp-procedures-28nov16/pdfYWMiLvnODO.pdf">
comment</a> seeks that any review of an IRP decision can only be made in a court and expresses concern about a standing panel of “ICANN insiders.” Again, however, the bylaws on this have been adopted.<o:p></o:p></span></p>
<p class="MsoListParagraphCxSpMiddle" style="margin-bottom:10.0pt;mso-add-space:auto;line-height:115%">
<span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoListParagraphCxSpMiddle" style="margin-bottom:10.0pt;mso-add-space:auto;text-indent:-.25in;line-height:115%;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif"><span style="mso-list:Ignore">5.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif">INTA’s
<a href="https://forum.icann.org/lists/comments-irp-supp-procedures-28nov16/pdfyVMCP8h4dU.pdf">
comment</a> seeks to enlarge the bylaws’ concept of standing and allow those to be claimants who not only have suffered harm but who are at risk of imminent harm. Again, this would entail changing the bylaws in my opinion.
<o:p></o:p></span></p>
<p class="MsoListParagraphCxSpMiddle"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoListParagraphCxSpLast" style="margin-bottom:10.0pt;mso-add-space:auto;text-indent:-.25in;line-height:115%;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif"><span style="mso-list:Ignore">6.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;line-height:115%;font-family:"Calibri",sans-serif">And Auerbach’s
<a href="https://forum.icann.org/lists/comments-irp-supp-procedures-28nov16/msg00003.html">
comment</a> says that “materially affected” is too stringent for standing and that a party should be able to bring an IRP claim should be broadened (e.g. to at least include anyone using an IP address or domain name, - in fact it should include “everyone”).
But this is a bylaw provision.<o:p></o:p></span></p>
<p class="MsoNormal">David<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">David McAuley<o:p></o:p></p>
<p class="MsoNormal">International Policy Manager<o:p></o:p></p>
<p class="MsoNormal">Verisign Inc.<o:p></o:p></p>
<p class="MsoNormal">703-948-4154<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>