<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body dir="auto">
<div>Hi Narelle, </div>
<div><br>
</div>
<div>In my view, it does not obviate the need for our statement. If the message included references to the ICANN Board AND the ICANN staff, then perhaps. But it doesn't.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Keith</div>
<div><br>
On May 6, 2015, at 11:02 PM, Narelle Clark <<a href="mailto:narelle.clark@accan.org.au">narelle.clark@accan.org.au</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Doesn’t this message obviate the need for any statement from us?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Ie doesn’t it answer the question that we’re posing about concerns ICANN has?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Narelle<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<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 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Internal-cg [<a href="mailto:internal-cg-bounces@ianacg.org">mailto:internal-cg-bounces@ianacg.org</a>]
<b>On Behalf Of </b>Alissa Cooper<br>
<b>Sent:</b> Thursday, 7 May 2015 10:48 AM<br>
<b>To:</b> ICG<br>
<b>Subject:</b> [Internal-cg] Fwd: [CCWG-ACCT] Further comment on concerns that ICANN will reject community developed proposals<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">FYI<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
Begin forwarded message:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b>From:</b> Bruce Tonkin <<a href="mailto:Bruce.Tonkin@melbourneit.com.au">Bruce.Tonkin@melbourneit.com.au</a>><br>
<b>Date:</b> May 6, 2015 at 3:19:59 PM PDT<br>
<b>To:</b> "<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>" <<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>><br>
<b>Subject:</b> <b>[CCWG-ACCT] Further comment on concerns that ICANN will reject community developed proposals</b><o:p></o:p></p>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Hello All,<br>
<br>
<br>
Regarding the following statement posted in numerous lists:<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">"ICANN has verbally represented that they will reject any proposed  agreement in which ICANN is not deemed the sole source prime  contractor for the IANA functions in perpetuity."<o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><br>
The ICANN Board supports the community processes that have been used to develop proposals for the IANA transition and ICANN's accountability.    ICANN also recognizes and accepts that the community will want to have fall back mechanisms in place should the
 IANA functions operator not perform its function to the standards required  by the community.   An important part of any system that focusses on security and stability is to document processes for handling any failures of the system.<br>
<br>
The Board also supports the need for the ICG to coordinate the various transition proposals, and awaits the outcome of that process.<br>
<br>
The Board will consider the recent reports from the CWG and CCWG that are open for public comment, and will raise any concerns it has in writing.   We urge other community members to focus on the documents produced by the cross-community working groups, and
 provide feedback to the cross-community working groups through the public comment process.<br>
<br>
Regards,<br>
Bruce Tonkin<br>
<br>
Board Liaison to the CCWG on Accountability<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><o:p></o:p></p>
</div>
</blockquote>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>Internal-cg mailing list</span><br>
<span><a href="mailto:Internal-cg@mm.ianacg.org">Internal-cg@mm.ianacg.org</a></span><br>
<span><a href="http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org">http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org</a></span><br>
<span></span><br>
<span></span><br>
</div>
</blockquote>
</body>
</html>