<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
+2 Milton, and you pointed out some truly disturbing problems about
two weeks ago. <br>
As for me, I am shocked at the tremendous revision to the bylaws
being introduced. <br>
I had thought we were adjusting accountability, not rewriting
ICANN's structure. <br>
- Kathy<br>
<br>
<div class="moz-cite-prefix">On 4/22/2016 10:50 AM, Matthew Shears
wrote:<br>
</div>
<blockquote cite="mid:571A3A1C.8090807@cdt.org" type="cite">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
+ 1 Milton<br>
<br>
<div class="moz-cite-prefix">On 4/22/2016 3:44 PM, Mueller, Milton
L wrote:<br>
</div>
<blockquote
cite="mid:BL2PR07MB2404AB0C0DC6C17665578528A16F0@BL2PR07MB2404.namprd07.prod.outlook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;}
@font-face
{font-family:"Source Sans Pro";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:24.0pt;
font-family:"Times New Roman",serif;
font-weight:bold;}
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:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Calibri Light",sans-serif;
color:#2E74B5;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Yes,
Aarti, we are not able to change the basic proposal. <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,
I wonder what would happen if someone discovers some major
“gotcha” that creates legal issues or some kinds of
internal contradictions. So the overall proposal must, I
think, be assessed in terms of its workability and not
just in terms of its adherence to the CCWG proposal. <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">--MM<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 style="border:none;border-left:solid blue
1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">
Ncuc-discuss [<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="mailto:ncuc-discuss-bounces@lists.ncuc.org">mailto:ncuc-discuss-bounces@lists.ncuc.org</a>]
<b>On Behalf Of </b>Aarti Bhavana<br>
<b>Sent:</b> Friday, April 22, 2016 3:20 AM<br>
<b>To:</b> Rafik Dammak <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:rafik.dammak@gmail.com"><rafik.dammak@gmail.com></a><br>
<b>Cc:</b> <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:ncuc-discuss@lists.ncuc.org">ncuc-discuss@lists.ncuc.org</a><br>
<b>Subject:</b> Re: [NCUC-DISCUSS] [info] Draft New
ICANN Bylaws Posted for Public Comment<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Hi Rafik,<o:p></o:p></p>
<p>The way I understand it, we are only looking at whether
the bylaws adequately reflect the principles in the final
proposal, that the chartering organisations agreed to.
This does not involve a substantive discussion itself, as
that has been closed. However, if anyone thinks that the
articulation of the bylaws haven't quite captured the
accountability-enhancing recommendations agreed upon in
the final proposal, then this is the perfect place to
raise these concerns. <o:p></o:p></p>
<p>Best,<br>
Aarti<o:p></o:p></p>
<div>
<p class="MsoNormal">On 22 Apr 2016 12:10 pm, "Rafik
Dammak" <<a moz-do-not-send="true"
href="mailto:rafik.dammak@gmail.com">rafik.dammak@gmail.com</a>>
wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC
1.0pt;padding:0in 0in 0in
6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal">Hi everyone,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I am sharing here the
announcement about public comment period for the
new ICANN bylaws challenges, which is part of the
implementation for the accountability proposals.
as you know the the accountability work is still
ongoing starting with the so-called "workstream
2". it doesn't look like when you read the
announcement, but this is another important step
to implement accountability measures within ICANN.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">hope that those from NCUC
involved in the CCWG can give some background and
explanations.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best Regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Rafik<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">----------
Forwarded message ----------<br>
<br>
<br>
<o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span
style="font-family:"Source Sans
Pro",sans-serif">Original link: </span><a
moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://www.icann.org/news/announcement-2016-04-21-en"><a class="moz-txt-link-freetext" href="https://www.icann.org/news/announcement-2016-04-21-en">https://www.icann.org/news/announcement-2016-04-21-en</a></a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div
style="mso-element:para-border-div;border:none;border-bottom:solid
#CFCFCF 1.0pt;padding:0in 0in 0in
0in;background:white">
<h1
style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:7.5pt;margin-left:0in;background:white;border:none;padding:0in;font-size:1.31rem;padding:1rem;font-weight:500!important"><span
style="font-family:"Helvetica",sans-serif;color:#333333">Draft
New ICANN Bylaws Posted for 30-day
Public Comment<o:p></o:p></span></h1>
</div>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Source Sans
Pro",sans-serif">Now that the IANA
Stewardship Transition Coordination
Group (ICG) and Cross Community Working
Group on Enhancing ICANN Accountability
(CCWG-Accountability) proposals have
been transmitted to NTIA, one of the key
implementation planning items is to
amend the ICANN Bylaws to reflect the
recommendations in those Proposals. The
proposed draft of the New ICANN Bylaws
was developed collaboratively by the
ICANN legal team and the independent
counsel hired to advise the
CCWG-Accountability and the Cross
Community Working Group to Develop an
IANA Stewardship Transition Proposal on
Naming Related Functions
(CWG-Stewardship). In developing the
Draft New ICANN Bylaws, the attorneys
consulted a Bylaws Coordination Group
populated with both community and Board
members, as well as with the
CWG-Stewardship and the
CCWG-Accountability.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Source Sans
Pro",sans-serif">Both the
independent counsel to the community
groups and ICANN's General Counsel have
confirmed that the Draft New ICANN
Bylaws are consistent with the community
proposals relating to the IANA
Stewardship Transition.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Source Sans
Pro",sans-serif">These proposed
draft Bylaws, are out for a 30-day
public comment from 21 April – 21 May to
allow any interested party to review and
provide feedback. This timeline allows
for comments to be analyzed and
incorporated in time for a tentative 27
May adoption of the Bylaws by the ICANN
Board.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Source Sans
Pro",sans-serif">NTIA has stated
that it needs to see that changes to the
Bylaws have been adopted sufficient to
implement the Transition Proposals
before NTIA can complete its review of
the Transition Proposals. This public
comment period is designed to meet that
deadline.</span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="font-family:"Source Sans
Pro",sans-serif">Link: <a
moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://www.icann.org/public-comments/draft-new-bylaws-2016-04-21-en"><a class="moz-txt-link-freetext" href="https://www.icann.org/public-comments/draft-new-bylaws-2016-04-21-en">https://www.icann.org/public-comments/draft-new-bylaws-2016-04-21-en</a></a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Source Sans
Pro",sans-serif;color:#888888"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Source Sans
Pro",sans-serif;color:#888888"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Ncuc-discuss mailing list<br>
<a moz-do-not-send="true"
href="mailto:Ncuc-discuss@lists.ncuc.org">Ncuc-discuss@lists.ncuc.org</a><br>
<a moz-do-not-send="true"
href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss"
target="_blank">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Ncuc-discuss mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Ncuc-discuss@lists.ncuc.org">Ncuc-discuss@lists.ncuc.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Matthew Shears | Director, Global Internet Policy & Human Rights Project
Center for Democracy & Technology | cdt.org
E: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:mshears@cdt.org">mshears@cdt.org</a> | T: +44.771.247.2987
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Ncuc-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ncuc-discuss@lists.ncuc.org">Ncuc-discuss@lists.ncuc.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss</a>
</pre>
</blockquote>
<br>
</body>
</html>