<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;}
--></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">As you know, we <a href="https://community.icann.org/display/IRPIOTI/IOT+Meeting+%2345+%7C+13+December+2018+@+19%3A00+UTC">
met</a> in December to discuss the challenge to ICANN staff participation as a co-equal participant in the IOT. And as you will recall, there was a split among us on the merits of the challenge.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="background:white">In my view, a challenge to the nature of participation of ICANN staff in the IOT is best resolved by ICANN in consultation with SOs and ACs.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="background:white"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="background:white">As a consequence, I suggest that we forward this issue to ICANN Org, with a copy to SO and AC leaders, as per the proposed letter below.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="background:white"><o:p> </o:p></span></p>
<p class="MsoNormal">In my personal view, the call we had in December and related emails have created a fair record for consideration.
<span style="background:white"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="background:white"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="background:white">I am interested in your feedback and request that any such feedback be posted on list as quickly as you can.
<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="background:white"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span style="background:white">Many thanks<o:p></o:p></span></p>
<p class="MsoNormal"><span style="background:white">David<o:p></o:p></span></p>
<p class="MsoNormal"><span style="background:white"><o:p> </o:p></span></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><span style="color:red">DRAFT LETTER FROM IOT TO:<o:p></o:p></span></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">ICANN Org CEO, Göran Marby<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">WITH COPY TO:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">ICANN Board Chair; SO/AC leaders<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dear Göran, and SO and AC leaders:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I am writing to you in my capacity as lead<span style="color:#1F497D">
</span>of the IRP <a href="https://community.icann.org/display/IRPIOTI/Independent+Review+Process+-+Implementation+Oversight+Team+%28IRP-IOT%29+Home">
Implementation Oversight Team</a>. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The IRP-IOT was originally established by the CCWG-Accountability and then was ‘adopted’ as such by the ICANN Bylaws in October, 2016, as per the provisions of Bylaw Section 4.3(n). In particular, Section 4.3(n)(i) provides in part:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><i><span style="background:white">An IRP Implementation Oversight Team shall be established in consultation with the </span>Supporting Organizations<span style="background:white"> and </span>Advisory Committees<span style="background:white"> and
comprised of members of the global Internet community. …<o:p></o:p></span></i></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We have been working on the development of Supplementary Procedures for IRP. The Board adopted the Interim Supplementary Procedures proposed by the IRP-IOT in October, 2018.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We have more work to do<span style="color:#1F497D"> </span>under Bylaw Section 4.3, including the finalization of the Supplementary Procedures. However, one of our members has lodged a formal challenge to the participation within the IOT
by ICANN staff as a co-equal participant. This challenge can be seen in this email:
<a href="https://mm.icann.org/pipermail/iot/2018-December/000472.html">https://mm.icann.org/pipermail/iot/2018-December/000472.html</a><span style="color:#1F497D">.
</span>In addition, the challenge was discussed at our IRP-IOT <a href="https://community.icann.org/display/IRPIOTI/IOT+Meeting+%2345+%7C+13+December+2018+@+19%3A00+UTC">
meeting</a> of December 13<sup>th</sup>, 2018. <span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The IOT has considered and agreed that a challenge of this nature may best be resolved by ICANN in consultation with the SOs and ACs.
<span style="color:#1F497D"> </span>Therefore, we request that this challenge be considered by ICANN in consultations with SOs and ACs and a resolution be notified to us so that we can proceed with our work.
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The IOT has one additional request to make of ICANN. <span style="color:#1F497D">
</span>The IOT has also discussed and agreed that we would benefit by having more members who would be willing to help in this important work. This, too, is a matter for ICANN to manage in consultation with SOs and ACs under the same bylaw provision. This
may be an opportune time to take steps toward that end, so please let me know if the IOT can assist in this process.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>