<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)"><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:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
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:"Markeringsbobletekst Tegn";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
mso-fareast-language:EN-US;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.MarkeringsbobletekstTegn
{mso-style-name:"Markeringsbobletekst Tegn";
mso-style-priority:99;
mso-style-link:Markeringsbobletekst;
font-family:"Tahoma","sans-serif";
mso-fareast-language:EN-US;}
span.EmailStyle21
{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:3.0cm 2.0cm 3.0cm 2.0cm;}
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-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Hi All,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I realise that I never sent this to you – just made it ready for sending – better late than never….<o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal>As promised at the last CWG call, we send you a written update on the item 5-7 on the agenda.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>5. CCWG-Accountability <o:p></o:p></b></p><p class=MsoNormal>a. Phrasing conditionality in the CWG Proposal <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As instructed by the Client Committee Wednesday 3<sup>rd</sup> June, Sidley has phrased the conditionality so that if the requirement are not met then the proposal will require revision. Jonathan sent Sidley’s rider and their comments to the CWG proposal to the CWG group Thursday 4<sup>th</sup> of June. Please read it and we will discuss it during the next call Tuesday 9<sup>th</sup> of June.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>b. CCWG-Accountability Public Comment closed yesterday <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The CWG chairs have sent comments to the CCWG draft proposal to the chairs of the CCWG and submitted it. Jonathan sent a copy of the comments to the CWG group on Wednesday 3<sup>rd</sup> June.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>6. Overall Timeline / Milestones<o:p></o:p></b></p><p class=MsoNormal>a. Communications and c. Sessions at ICANN 53<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Regarding the communication it is important that participants and members help educating and informing the community regarding the proposal – you are ambassadors for our work. We have all made great efforts and sacrifices in order to build a solid well-considered piece of work that of course and necessarily contain compromises. Now we need to you all to inform and educate the different groups to aide in consideration for approval and support in BA.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>b. Webinars on 11 June<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>There will be two webinars on Thursday 11th of June. The CWG-chair will run the webinars - one during the morning and one early afternoon. The webinars will be based on a slide-deck, that we will send to the CWG group to use for educating their respective SO or AC and once more we encourage you all to use the slides. We will have help from Xplane in doing the graphics to have a comprehensive and explanatory set of slides.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We have decides to offer live interpretation, but participants need to sign up for interpretation before the webinar.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>7. Client Committee - Instructions to Sidley<o:p></o:p></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Wednesday 3<sup>rd</sup> June the Client Committee sent instructions to Sidley regarding:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>1. The CWG’s requirements in order to finish the proposal<o:p></o:p></p><p class=MsoNormal>2. The CWG’s requirements to support the proposal in B.A.<o:p></o:p></p><p class=MsoNormal>3. The CWG’s potential requirements post B.A. and/or with implementation<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The following need to be secured by Sidley in advance of concluding the final proposal for send-off next week.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>A. A form of language which effectively captures the conditional nature of the proposal i.e. that the proposal is valid if and only if adequate accountability mechanisms are in place. These mechanisms are currently contemplated by the CWG in conjunction with the CCWG<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>B. A confirmation around the use (or not) of the ICANN bylaws as described in the CWG proposal in order to capture the necessary components of the CWG proposal that need to be enshrined in the ICANN bylaws.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>C. A confirmation that the final proposal is consistent with Sidley’s advice given to date and, to the extent that it is not, what changes are required.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The CWG chairs find that the response from Sidley from 4<sup>th</sup> June includes all these issues. As mentioned earlier this is to be discussed during the third reading of the proposal on Tuesday 9<sup>th</sup> June.<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><o:p> </o:p></p><p class=MsoNormal>Jonathan and Lise<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>