<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;}
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:1840385793;
mso-list-type:hybrid;
mso-list-template-ids:-1770849092 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">I mentioned in my email of this past Tuesday that we might be able to agree a rule on elements today, if possible.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In that respect, please see my <a href="https://mm.icann.org/pipermail/iot/2018-April/000379.html">
email</a> of April 10<sup>th</sup> and Kavouss’s <a href="https://mm.icann.org/pipermail/iot/2018-April/000380.html">
email</a> of the same date. These will give you the background and original recommendation.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">On elements here is what I propose now, with my attempt to take into account a matter that Kavouss raised:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">That we add a new section under the definition of DISPUTES in ‘section 1. Definitions’ in the draft
<a href="https://www.icann.org/en/system/files/files/draft-irp-supp-procedures-31oct16-en.pdf">
Updated Supplementary Procedures</a> as follows:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>(D) A written statement of a DISPUTE shall contain at least the following information:<o:p></o:p></b></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%;mso-list:l0 level1 lfo1">
<b>A demand that the DISPUTE be referred to Independent Review pursuant to Bylaw section 4.3 (or Annex D, Section 4.2 for Empowered Community claims);<o:p></o:p></b></li><li class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%;mso-list:l0 level1 lfo1">
<b>A reference to any ICANN contract, ICANN policy, ICANN action or inaction, or decision by a process-specific expert panel out of or in relation to which the DISPUTE arises;
<o:p></o:p></b></li><li class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%;mso-list:l0 level1 lfo1">
<b>A description of the claim and the facts supporting it and how such contract, policy, action or inaction, or decision violate(s) ICANN’s Articles of Incorporation or Bylaws; and<o:p></o:p></b></li><li class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%;mso-list:l0 level1 lfo1">
<b>A reference </b><b><span style="color:black">to any similar claims already submitted to IRP together the resulting decisions, if rendered, that the Claimant is aware of.
</span></b><b><o:p></o:p></b></li></ol>
<p class="MsoNormal">These elements don’t address PTI service complaints or IANA Naming Functions contract complaints, but we can address that when the IOT later addresses any ‘specialized’ rules noted in Bylaw 4.3(n)(ii).
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I regret that I have been unable yet to take a stab at ‘Types of Hearings’ in light of my original suggestion and Malcolm’s comment – but I will send that to list in the coming week.<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">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">Sr International Policy & Business Development 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>