<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=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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
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
{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;}
span.hoenzb
{mso-style-name:hoenzb;}
span.E-MailFormatvorlage19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
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="DE-CH" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Dear all<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">As I said before I share these concerns.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Regards<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Jorge
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Von:</span></b><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> cwg-stewardship-bounces@icann.org [mailto:cwg-stewardship-bounces@icann.org]
<b>Im Auftrag von </b>Kavouss Arasteh<br>
<b>Gesendet:</b> Sonntag, 10. April 2016 14:21<br>
<b>An:</b> Greg Shatan <gregshatanipc@gmail.com><br>
<b>Cc:</b> cwg-stewardship@icann.org IANA <cwg-stewardship@icann.org>; accountability-cross-community@icann.org Accountability <accountability-cross-community@icann.org><br>
<b>Betreff:</b> Re: [CWG-Stewardship] [CCWG-ACCT] [bylaws-coord] DRAFT NEW ICANN BYLAWS - 2 April 2016 version - SCWG<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Dear All,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">As I intervened at call ,I am not in favour of MAJORITY for the reasons mentioned by others ,in particular, Greg.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">We should not allow the entire community be captured by one or two constituency or sub constituency<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Regards<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Kavouss <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">2016-04-10 0:41 GMT+02:00 Greg Shatan <<a href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a>>:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif">I agree with the concerns raised here regarding the use of a majority level of decision-making in the SCWG. The registries (with 6 seats) nearly hold a majority, and as Seun notes, the registries/registrars
do hold a majority. This by itself is probably enough to disqualify a majority as an appropriate measure. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif">Consensus would be far more appropriate (I don't think this needs to be "full consensus," however). After all, nearly every decision-making process in ICANN-land is some form of consensus.
(While the GNSO Council is an exception, many Council decisions involve things such as PDP reports that are themselves the product of consensus. The Board is another significant exception, but the Board often operates by de facto consensus.)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif;color:#888888"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif;color:#888888">Greg<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Sat, Apr 9, 2016 at 12:44 PM, Kavouss Arasteh <<a href="mailto:kavouss.arasteh@gmail.com" target="_blank">kavouss.arasteh@gmail.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class="MsoNormal">Dear Colleagues<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">We all were very busy and a small number of very specifically oriented influence the entire procedure by putting a sentence or phrase that, in the absent of
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">consensus, the majority is prevails.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">THIS IS NOT ACCEPTABLE.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">By so doing the rest of the community would be captured by few influençai constituency.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">We MUST stick to the consensus and it is up to the chair or convener of the group to seek that consensus.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">We have discussed this issue at ICG in fall 2014 and produced a document under " Consensus Building Process2<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">That served as a guide line during the ICG debate<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Those proposed MAJORITY here proposed Full consensus ELSEWHERE<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">DOUBLE STANDARD depending ON WHICH DIRECTION THEY WISH THAT THE WIND BLOWS.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">NO AND NO<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">This is unacceptable<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Regards<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#888888">Kavouss <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#888888"><o:p> </o:p></span></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">2016-04-09 17:54 GMT+02:00 Christopher Wilkinson <<a href="mailto:lists@christopherwilkinson.eu" target="_blank">lists@christopherwilkinson.eu</a>>:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p class="MsoNormal">Well, Chuck, where I come out on this:<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">1. I agree that it should be harder.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">2. The proposed voting structure of SCWG is so far biassed towards GNSO and the Registries, that the 'small group' could actually represent all the governments (one vote) and all the users (one vote). If the composition of the SCWG was
balanced 50:50 then one might consider a simple majority of all the members, 50%+1. But as it stands in the proposal, well, NO.<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"><span style="color:#888888"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#888888">CW<o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">On 05 Apr 2016, at 21:32, "Gomes, Chuck" <<a href="mailto:cgomes@verisign.com" target="_blank">cgomes@verisign.com</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I think there are two ways of looking at this:</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div style="margin-left:36.0pt">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">1.</span><span lang="EN-US" style="font-size:7.0pt;color:#1F497D"> </span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Requiring
consensus makes it harder to do separation. As Christopher says, that is a big step so maybe it should be harder. That is in essence why I opposed only requiring a simple majority of those present in a meeting instead of a simple majority of all members
whether they are in attendance or not.</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div style="margin-left:36.0pt">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">2.</span><span lang="EN-US" style="font-size:7.0pt;color:#1F497D"> </span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Requiring
consensus also makes it easier for a small group to essentially veto a separation recommendation. If a small group of the members oppose a separation while a strong majority favor it, simply by preventing consensus, separation could be stopped.</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I don’t know where I come out on this but I definitely we should weigh both points before deciding.</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Chuck</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<div>
<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"> <a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank"><span style="color:purple">cwg-stewardship-bounces@icann.org</span></a> [mailto:<a href="mailto:cwg-" target="_blank">cwg-</a><a href="mailto:stewardship-bounces@icann.org" target="_blank"><span style="color:purple">stewardship-bounces@icann.org</span></a>] <b>On
Behalf Of </b>Christopher Wilkinson<br>
<b>Sent:</b> Tuesday, April 05, 2016 2:41 PM<br>
<b>To:</b> <a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a> Accountability<br>
<b>Cc:</b> <a href="mailto:cwg-stewardship@icann.org" target="_blank"><span style="color:purple">cwg-stewardship@icann.org</span></a> IANA<br>
<b>Subject:</b> [CWG-Stewardship] Fwd: [CCWG-ACCT] [bylaws-coord] DRAFT NEW ICANN BYLAWS - 2 April 2016 version - SCWG<br>
<b>Importance:</b> High</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt">Good evening:</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt">With reference to the Sidley draft of April 2, 2016 ("Questions and Clarifications for Bylaws Coordination Group"), I wish to make a specific comment relating to Question 22 referring to Section
19 of the draft Bylaws concerning the SCWG ("Separation Cross Community Working Group".)</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt">Section 19.5 addresses the Composition of the SCWG and the voting rights of its members and liaisons.</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt">Section 19.7 (a) addresses the SCWG decision-making procedure.</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt">During the CWG conference call on April 4, Sidley raised the issue of how to define the majority of the SCWG (Section 19.7(a)) in the absence of a consensus. </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt">The bar of 50+1% was proposed. (Question 22.)</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:13.0pt">I submit that this bar is far too low, and that the general principle of consensus must be maintained.</span></b><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt">Section 19.5 of the draft Bylaws provides for SCWG to be composed of 13 voting members, 5 non voting liaisons and unlimited other participants. Among the voting members, GNSO and the ccTLDs would
hold 9 votes; more than a majority of 7.</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt">However, eventual separation of the IANA/PTI function from ICANN would have far reaching implications for many stakeholders which go well beyond the specific interests of DNS Registries and Registrars.</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt">It would not be appropriate for the representatives of the Registries and Registrars to be able to determine a separation decision, acting alone, absent consensus in the SCWG. If the proposed
composition and voting rights in an SCWG are maintained, it is absolutely essential that the SCWG act by consensus and not by a majority vote.</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt">Regards</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:13.0pt">Christopher Wilkinson</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">Begin forwarded message:<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:13.5pt;font-family:"Helvetica",sans-serif">From: </span></b><span lang="EN-US" style="font-size:13.5pt;font-family:"Helvetica",sans-serif">Mathieu Weill <<a href="mailto:mathieu.weill@afnic.fr" target="_blank"><span style="color:purple">mathieu.weill@afnic.fr</span></a>></span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:13.5pt;font-family:"Helvetica",sans-serif">Subject: [CCWG-ACCT] Fwd: [bylaws-coord] DRAFT NEW ICANN BYLAWS - 2 April 2016 version</span></b><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:13.5pt;font-family:"Helvetica",sans-serif">Date: </span></b><span lang="EN-US" style="font-size:13.5pt;font-family:"Helvetica",sans-serif">3 Apr 2016 14:16:21 GMT+02:00</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:13.5pt;font-family:"Helvetica",sans-serif">To: </span></b><span lang="EN-US" style="font-size:13.5pt;font-family:"Helvetica",sans-serif">CCWG Accountability <<a href="mailto:accountability-cross-community@icann.org" target="_blank"><span style="color:purple">accountability-cross-community@icann.org</span></a>></span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">Dear colleagues, <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">In anticipation of our calls this week, please find below a note from the lawyers group, the draft bylaws as well as an issue list. <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">It is important to read the lawyers notes as they quite efficiently describe the context and status of the work. Please review them for any process related question. <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">The purpose of our calls this week will be to address the issue list questions (questions 1-7 & 25-34 are for the CCWG, the others for CWG). <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">Should any other issue be added to the list based on your respective reviews, please raise your questions on the list for transparency. <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US">Best regards,<o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">Mathieu<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">---------------<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">Depuis mon mobile, d</span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US">sol</span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US"> pour le
style<o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><br>
D</span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US">but du message transf</span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US">r</span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US"> :<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span lang="EN-US">Exp</span></b><b><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span></b><b><span lang="EN-US">diteur:</span></b><span lang="EN-US"> John Jeffrey via bylaws-coord <<a href="mailto:bylaws-coord@icann.org" target="_blank"><span style="color:purple">bylaws-coord@icann.org</span></a>><br>
<b>Date:</b> 3 avril 2016 13:16:28 UTC+2<br>
<b>Destinataire:</b> <a href="mailto:bylaws-coord@icann.org" target="_blank"><span style="color:purple">bylaws-coord@icann.org</span></a><br>
<b>Cc:</b> "Flanagan, Sharon" <<a href="mailto:sflanagan@sidley.com" target="_blank"><span style="color:purple">sflanagan@sidley.com</span></a>>, "Cc: Zagorin, Janet S." <<a href="mailto:jzagorin@sidley.com" target="_blank"><span style="color:purple">jzagorin@sidley.com</span></a>>,
"Hilton, Tyler" <<a href="mailto:thilton@sidley.com" target="_blank"><span style="color:purple">thilton@sidley.com</span></a>>, ICANN-Adler <<a href="mailto:ICANN@adlercolvin.com" target="_blank"><span style="color:purple">ICANN@adlercolvin.com</span></a>>,
"Hofheimer, Joshua T." <<a href="mailto:jhofheimer@sidley.com" target="_blank"><span style="color:purple">jhofheimer@sidley.com</span></a>>, "Mohan, Vivek" <<a href="mailto:vivek.mohan@sidley.com" target="_blank"><span style="color:purple">vivek.mohan@sidley.com</span></a>>,
"Clark, Michael A." <<a href="mailto:mclark@sidley.com" target="_blank"><span style="color:purple">mclark@sidley.com</span></a>>, "Boucher, Rick" <<a href="mailto:rboucher@sidley.com" target="_blank"><span style="color:purple">rboucher@sidley.com</span></a>>,
Sidley ICANN CCWG <<a href="mailto:sidleyicannccwg@sidley.com" target="_blank"><span style="color:purple">sidleyicannccwg@sidley.com</span></a>>, "Kerry, Cameron" <<a href="mailto:ckerry@sidley.com" target="_blank"><span style="color:purple">ckerry@sidley.com</span></a>>,
"McNicholas, Edward R." <<a href="mailto:emcnicholas@sidley.com" target="_blank"><span style="color:purple">emcnicholas@sidley.com</span></a>>, Daniel Halloran <<a href="mailto:daniel.halloran@icann.org" target="_blank"><span style="color:purple">daniel.halloran@icann.org</span></a>>,
Amy Stathos <<a href="mailto:amy.stathos@icann.org" target="_blank"><span style="color:purple">amy.stathos@icann.org</span></a>>, "Boelter, Jessica C.K." <<a href="mailto:jboelter@sidley.com" target="_blank"><span style="color:purple">jboelter@sidley.com</span></a>>,
"Fuller, Miles" <<a href="mailto:wfuller@sidley.com" target="_blank"><span style="color:purple">wfuller@sidley.com</span></a>>, "Tam, Tennie H." <<a href="mailto:tennie.tam@sidley.com" target="_blank"><span style="color:purple">tennie.tam@sidley.com</span></a>><br>
<b>Objet:</b> <b>[bylaws-coord] DRAFT NEW ICANN BYLAWS - 2 April 2016 version</b><br>
<b>R</b></span><b><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span></b><b><span lang="EN-US">pondre </span></b><b><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span></b><b><span lang="EN-US">:</span></b><span lang="EN-US"> John
Jeffrey <<a href="mailto:john.jeffrey@icann.org" target="_blank"><span style="color:purple">john.jeffrey@icann.org</span></a>><o:p></o:p></span></p>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p><span lang="EN-US">Dear Bylaws Coordination Group,<o:p></o:p></span></p>
<p><span lang="EN-US">Please find attached a document </span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US"> DRAFT NEW ICANN BYLAWS (vers. 2Apr) (</span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US">DRAFT
BYLAWS</span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US">) for your review and discussion. As you will recall the last full draft was provided to you on 18 March, with the promise to provide another full turn of the
DRAFT BYLAWS for your review today on 2 April. The DRAFT BYLAWS attached is the current working draft among the legal drafting group. There is also an Issue List attached, which are a set of additional questions and clarifications requested from the Bylaws
Coordination Group.<o:p></o:p></span></p>
<p><span lang="EN-US"> We ask that you share the attachments with your CCWG, ICG and CWG colleagues who will be reviewing this during this critical work week<o:p></o:p></span></p>
<p><b><u><span lang="EN-US">Recent Work</span></u></b><span lang="EN-US"> </span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US"> During the past two weeks the legal drafting group, made up of Sidley</span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US">s
team, Adler</span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US">s team and ICANN's Legal team reviewed and worked through mark ups and redrafts of the various sections of new ICANN Bylaws. Also, we have held four separate
meetings with the Bylaws Coordination Group during this two-week period asking questions and incorporating that feedback into the new draft. There is likely to be the need for some additional discussions as we work toward a public comment version of the new
ICANN bylaws.<o:p></o:p></span></p>
<p><b><u><span lang="EN-US">More Work to Do</span></u></b><span lang="EN-US"> </span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US"> There is still work to do on the DRAFT BYLAWS, in identifying and working through any
remaining provisions in the draft that are not clear, finding any remaining open issues, improving the provisions, and polishing the draft before publication for public comment. The legal teams remain engaged in review mode and are available for questions
and comments during this period.<o:p></o:p></span></p>
<p><b><u><span lang="EN-US">Legal Teams have not yet </span></u></b><b><u><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span></u></b><b><u><span lang="EN-US">certified</span></u></b><b><u><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span></u></b><span lang="EN-US"> </span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US"> Since
a) the Bylaws Coordination Group, CWG and CCWG have not yet reviewed and reacted to these DRAFT BYLAWS, b) there are still remaining open issues, and c) there is still review and polishing to be done by the legal teams </span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US"> the
legal teams have not indicated yet that the current DRAFT BYLAWS fully meets the recommendations within the Proposals.<o:p></o:p></span></p>
<p><span lang="EN-US">As we have indicated above there is still work to be done, including receiving the feedback from those reviewing these DRAFT BYLAWS this week before the legal teams will be in a position to certify the posting version for Public Comment<o:p></o:p></span></p>
<p><b><u><span lang="EN-US">Next Steps</span></u></b><span lang="EN-US"> </span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US">1) <i>Now until 13 April</i> </span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US"> members of CCWG, CWG, Bylaws Coordination Group, Board and ICG to complete review of these DRAFT BYLAWS and provide
feedback to legal teams;<o:p></o:p></span></p>
<p><span lang="EN-US">2) <i>Now until 18 April</i>, (with particular focus during week of 13-18 April) </span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US"> legal teams to update DRAFT BYLAWS working in coordination
with the Bylaws Drafting Group;<o:p></o:p></span></p>
<p><span lang="EN-US">3) <i>20 April</i> </span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US"> posting date for public comment period for new proposed bylaws </span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US"> with
legal teams supporting that the new proposed bylaws meets the proposal recommendations.<o:p></o:p></span></p>
<p><span lang="EN-US" style="font-family:"Tahoma",sans-serif">���</span><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US">As before, we look forward to working with all of you in the coming days, to get ICANN</span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US">s Bylaws in the best form possible to effectuate these important
changes.<o:p></o:p></span></p>
<p><span lang="EN-US">We hope these views of the documents are useful and that you receive them in the spirit that they are offered</span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US"> to help all of us to be able to
collaborate and work through these Bylaws changes in the most effective way possible </span><span lang="EN-US" style="font-family:"Tahoma",sans-serif">�</span><span lang="EN-US"> to enable the creation of a new and stronger, community empowered ICANN.<o:p></o:p></span></p>
<p><span lang="EN-US">John Jeffrey, Holly Gregory, and Rosemary Fei<o:p></o:p></span></p>
</blockquote>
</div>
</div>
</div>
<div>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US">_____________________<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">____________________<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US">_______________________________________________<br>
bylaws-coord mailing list<br>
<a href="mailto:bylaws-coord@icann.org" target="_blank"><span style="color:purple">bylaws-coord@icann.org</span></a><br>
<a href="https://mm.icann.org/mailman/listinfo/bylaws-coord" target="_blank"><span style="color:purple">https://mm.icann.org/mailman/listinfo/bylaws-coord</span></a><o:p></o:p></span></p>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank"><span style="color:purple">Accountability-Cross-Community@icann.org</span></a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank"><span style="color:purple">https://mm.icann.org/mailman/listinfo/accountability-cross-community</span></a><o:p></o:p></span></p>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>