<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=iso-8859-1">
<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:149371230;
mso-list-type:hybrid;
mso-list-template-ids:-951690834 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">Here below is suggested text of a letter we might send to SO/AC leaders in order to seek new members to IOT. I’d like to discuss on call tomorrow.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best wishes,<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>
<p class="MsoNormal"><b>Here is suggested text:<o:p></o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dear Supporting Organizations and Advisory Committees leaders:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">[<span style="background:yellow;mso-highlight:yellow">With copy to: Göran, JJ, David Olive, Board</span>]<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We are writing to you to ask that you help us in adding new members to the ICANN Independent Review Process Implementation Oversight Team (IRP-IOT).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The IRP-IOT was created by the CCWG Accountability to develop rules of procedure for the Independent Review Process (IRP). The IRP is a formal arbitration mechanism that is ICANN’s highest form of internal dispute resolution procedure.
It is addressed in Section 4.3 of ICANN’s bylaws. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The IRP-IOT was later adopted by the ICANN Bylaws that became effective in October 2016, as part of the IANA Transition – specifically Bylaw 4.3(n)(i), which states, in part:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><i><span style="color:#333333;background:white"><o:p> </o:p></span></i></p>
<p class="MsoNormal" style="margin-left:.5in"><i><span style="color:#333333;background:white">An IRP Implementation Oversight Team shall be established in consultation with the </span>Supporting Organizations<span style="color:#333333;background:white"> and </span>Advisory
Committees<span style="color:#333333;background:white"> and comprised of members of the global Internet community. </span>
<o:p></o:p></i></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The IRP-IOT is about to wrap-up work on ‘supplementary’ rules of procedure that supplement the rules of the International Centre for Dispute Resolution (ICDR) so as to take account of ICANN’s unique nature. ICDR is ICANN’s IRP services
provider. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">But our membership has been dwindling and we have remaining work to do as tasked to us under the bylaws:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%;mso-list:l0 level2 lfo1">
Cooperative Engagement Process rules to be developed – see section 4.3(i);<o:p></o:p></li><li class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%;mso-list:l0 level2 lfo1">
Possibly recommend panel training – see section 4.3(j)(i);<o:p></o:p></li><li class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%;mso-list:l0 level2 lfo1">
Develop an IRP panelist recall procedure – see section 4.3(j)(iii);<o:p></o:p></li><li class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%;mso-list:l0 level2 lfo1">
Possibly develop specialized PTI service-complaints rules – see section 4.3(n)(ii);<o:p></o:p></li><li class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%;mso-list:l0 level2 lfo1">
Develop procedures if ICANN elects not to respond to an IRP (see section 4.3(n)(iv)(F));<o:p></o:p></li><li class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%;mso-list:l0 level2 lfo1">
Develop standards and rules governing appeals (see section 4.3(n)(iv)(G) and see also section 4.3(w));<o:p></o:p></li><li class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%;mso-list:l0 level2 lfo1">
Possibly develop additional independence requirements for IRP panelists – see section 4.3(q)(i)(B). This includes consideration of term limits and restrictions on post-term appointments to other ICANN positions – see 4.3(q)(i)(B) and see 4.3(j)(iii).<o:p></o:p></li></ol>
</ol>
<p class="MsoNormal">We therefore wish to add members as soon as possible – we are planning for a meeting at ICANN 64 that will be in that nature of a re-organizational meeting and with a view to work on substance as outlined above.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As you saw above, the IOT shall be established in consultation with SOs and ACs. We suggest that each SO/AC seek to add [<span style="color:red">two, three – what number do we think is best</span>] members from your organizations to the
IOT. We have suggested text below that could be useful in announcing this to your members:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">SUGGESTED TEXT:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The IRP-IOT was established by the CCWG Accountability and later by the ICANN Bylaws to help implement ICANN’s new Independent Review Process as established by the October 2016 Bylaws. The IRP is addressed in Bylaw Section 4.3 and the IOT
is described in Section 4.3(n)(i). <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The IOT is seeking new members through consultation with SOs and ACs. As you can see from Bylaw Section 4.3, the work is in large part dealing with legal matters. Legal training would be welcome but is not essential to join.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The IOT has asked each SO/AC to distribute this announcement to its members and each SO/AC is suggested to nominate
<span style="color:red">????</span> members, who can begin service as soon as possible. The IOT will be holding and organizational and substantive meeting at ICANN 64.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>