<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:0in;
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:0in;
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;
font-family:"Arial","sans-serif";
color:black;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">My apologies if you’re getting this twice; I couldn’t tell what list the reply I just sent actually went to.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Rosemary
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Rosemary E. Fei
<br>
<b>Sent:</b> Thursday, May 12, 2016 10:25 AM<br>
<b>To:</b> CCWG-Listserv<br>
<b>Cc:</b> ICANN-Adler; Sidley ICANN CCWG (sidleyicannccwg@sidley.com)<br>
<b>Subject:</b> RE: [CCWG-ACCT] CCWG-Accountability - V2.0 of comments on draft Bylaws - 24 hour Final Feedback by CCWG-Accountability<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Dear All:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">As CCWG’s legal counsel, we have no legal concerns if the CCWG prefers not to protect the existing Plans from challenge for exceeding ICANN’s Mission, but I did
want to clarify that, as drafted, ONLY the current versions of the Plans are so protected; NO renewals or future Plans, nor any amendments to the existing Plans, would have such protection under the language currently in the Draft Bylaws.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Our understanding was that these existing Plans are already in place and in operation, and had received appropriate community input when they were developed before
the new Bylaws apply, so that grandfathering them eliminated a source of potential harmful disruption without any clear corresponding benefit, from the transition. We viewed this as an implementation issue. However, as I said above, if the CCWG prefers not
to preclude challenges to the EXISTING Plans (and ONLY to the currently-existing Plans), we are happy to implement that change if so directed.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Rosemary<b> </b></span><b><o:p></o:p></b></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="3" width="100%" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a href="mailto:accountability-cross-community-bounces@icann.orgOn">accountability-cross-community-bounces@icann.orgOn</a> Behalf OfAndrew Sullivan<br>
<b>Sent:</b> Wednesday, May 11, 2016 12:10:54 PM (UTC-08:00) Pacific Time (US & Canada)<br>
<b>To:</b> <a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a><br>
<b>Subject:</b> Re: [CCWG-ACCT] CCWG-Accountability - V2.0 of comments on draft Bylaws - 24 hour Final Feedback by CCWG-Accountability</span><o:p></o:p></p>
<div>
<p class="MsoNormal">Hi,<br>
<br>
I note this does not ask that 1.1(d)(ii) E not be removed. I think<br>
that's the 5 year plans. How come that's ok to be grandfathered?<br>
Note that it's not the 5 year plans that exist now, but the ones to be<br>
adopted. I don't think the CCWG or CWG asked to grandfather those any<br>
more than they did the various outside agreements. I heartily agree<br>
with the point in the comments that "the implementation phase is not a<br>
time to incorporate new provisions that were not in the<br>
CCWG-Accountability Recommendations," and I think this is another<br>
example of it.<br>
<br>
Best regards,<br>
<br>
A<br>
<br>
On Wed, May 11, 2016 at 02:53:37PM -0400, Bernard Turcotte wrote:<br>
> All,<br>
> <br>
> Please find attached V2.0 of the CCWG-Accountability comments to be<br>
> submitted to the ICANN public consultation on the New Bylaws.<br>
> <br>
> Modifications since V1.0 was circulated (There is no red-line comparison as<br>
> too many things have changed. Rather we are providing a high level summary<br>
> of changes here and are providing both versions V1.0 and 2.0 for ease of<br>
> comparison):<br>
> <br>
> <br>
> - V1.0 items 9 and 10 have been removed following consideration of legal<br>
> counsel advice.<br>
> - 9. Draft Bylaws Annex D Section 1.4(b)<br>
> - 10. Draft Bylaws Annex D Section 2.2 (c) (i) (A)<br>
> - V2.0 new item 9 is - Draft Bylaws Section 1.2(b)(viii) which was<br>
> in the initial comments but not included in V1.0<br>
> - V2.0 new items 10 to 14. These are a selection by the leadership from<br>
> the list of issues submitted by Alan Greenberg this past weekend<br>
> - 10. Draft Bylaws Section 7.12 (b)<br>
> - 11. Draft Bylaws Section 4.6(b)(ii)<br>
> -<br>
> <br>
> 12. Draft Bylaws Section 7.4(d)<br>
> -<br>
> <br>
> 13. Draft Bylaws Section 7.11(a)(i)(B)<br>
> -<br>
> <br>
> 14. Draft Bylaws Annex D, Section 1.4(b)(i-ii)<br>
> - V2.0 New - Conclusion - short recap of Introduction<br>
> <br>
> The Final Feedback period is only intended to provide the<br>
> CCWG-Accountability participants the opportunity to confirm there are no<br>
> significant issues or gaps in this version and is not intended as an<br>
> opportunity to raise new issues.<br>
> <br>
> The Feedback period will begin 20:00UTC today Wednesday May 11th and close<br>
> 20:00UTC Thursday May 12th.<br>
> <br>
> Please reply to the list using the Subject line of this message to<br>
> facilitate identifying your input (or simply REPLY to this email).<br>
> <br>
> The objective of the leadership is to finalize these and submit them before<br>
> the weekend.<br>
> <br>
> Documents attached.<br>
> <br>
> Bernard Turcotte<br>
> ICANN Staff Support for the CCWG-Accountability Co-Chairs - Mathieu Weill,<br>
> Thomas Rickert, Leon Sanchez<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><br>
<br>
<br>
-- <br>
Andrew Sullivan<br>
<a href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><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>
</div>
</body>
</html>