<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 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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";
color:#330033;}
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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:#330033;}
span.EmailStyle18
{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]--></head><body bgcolor=white lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Avri,<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'>My personal view is that I am not yet convinced by the need for or perhaps do not adequately understand the need for the extra (CWG) step.<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'>However, as I understand your current wording, it seems to be a discretionary step that the IFR may choose to recommend to use or not.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Therefore, since it is therefore not “baked in” , I do not have major reservations.<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'>Thanks,<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'>Jonathan<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";color:windowtext'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> Avri Doria [mailto:avri@acm.org] <br><b>Sent:</b> 22 April 2015 15:19<br><b>To:</b> cwg-stewardship@icann.org<br><b>Subject:</b> Re: [CWG-Stewardship] [client com] CWG Meeting #42: Sidley Proposed Inserts<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi,<br><br>A suggested rewording that includes the steps I think were missed.<br><br>avri<br><br><o:p></o:p></p><p>On 21 Apr 2015 23:O04, "Client Committee List for CWG" <<a href="mailto:cwg-client@icann.org" target="_blank">cwg-client@icann.org</a>> wrote:<br>><br>> Dear All,<br>><br>> <br>><br>> Following up on today’s call, below is proposed language for III. A and Annex L.<br>><o:p></o:p></p><div><div><p class=MsoNormal>> Annex L:<br>><br>> <br>><br>> Triggers for the Separation Mechanism<br>><br>> An outcome of an IANA Function Review could include a recommendation to initiate a separation of the IANA Functions Operator. This recommendation would be submitted to the ICANN Board for consideration, with ultimate input by the multistakeholder community through the CCWG Accountability mechanisms under consideration.(1) <o:p></o:p></p></div></div><p class=MsoNormal><br>An outcome of an IANA Function Review could include a recommendation to initiate a Cross Community Working Group to make specific recommends that deal with recommendation made by the IFR. These could include the creation of an RFP and separation of the IANA Functions Operator. This would would be according toa cross community working group chartered by the Board and its recommendation would be submitted to the ICANN Board for consideration. The cross community process would include the collection of community input and intermediate comment periods on the work, with ultimate input by the multistakeholder community through the CCWG Accountability mechanisms under consideration.(1) <br><br><br><o:p></o:p></p><div><div><p class=MsoNormal>>> (1) A point for public comment is whether the IANA Function Review recommendation for separation should first be submitted to the Supporting Organizations and Advisory Committees for their approval before escalation to the ICANN Board, or whether the IANA Function Review recommendation for separation should be submitted directly to the ICANN Board by the IANA Function Review Team.<o:p></o:p></p></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><br>(1) A point for public comment is whether the IANA Function Review recommendation for a separation process should be chartered by the Board or by the SOAC and whether the recommendations should first be submitted to the Supporting Organizations and Advisory Committees for their approval before escalation to the ICANN Board. Or whether the Separation process CWG recommendation for separation should be submitted directly to the ICANN Board by the IANA Function Review Team.<br><br><br><o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=1 width="99%" noshade style='color:#909090' align=center></div><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 style='border-collapse:collapse'><tr><td style='padding:0cm 11.25pt 0cm 6.0pt'><p class=MsoNormal><a href="http://www.avast.com/"><span style='text-decoration:none'><img border=0 id="_x0000_i1026" src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo"></span></a><o:p></o:p></p></td><td style='padding:.75pt .75pt .75pt .75pt'><p><span style='font-family:"Calibri","sans-serif";color:#3D4D5A'>This email has been checked for viruses by Avast antivirus software. <br><a href="http://www.avast.com/">www.avast.com</a> <o:p></o:p></span></p></td></tr></table><p class=MsoNormal><o:p> </o:p></p></div></body></html>