<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 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: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
{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";}
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.EmailStyle20
{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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">And just for the record, I was not advocating or supporting the points, just pointing out what will need to be addressed and/or resolved in the next iteration
of our 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">Keith<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"><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""> Seun Ojedeji [mailto:seun.ojedeji@gmail.com]
<br>
<b>Sent:</b> Wednesday, September 30, 2015 1:25 PM<br>
<b>To:</b> Drazek, Keith<br>
<b>Cc:</b> accountability-cross-community@icann.org; Nigel Roberts<br>
<b>Subject:</b> Re: [CCWG-ACCT] A way to avoid the 'The Single Member Can Do Anything!' problem<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Thanks for this, and just for record, the list below is what I can naturally add my +1 to in its entirety. Every points are critical and the last is even more critical than any other one.<o:p></o:p></p>
<p>Cheers!<o:p></o:p></p>
<p>Sent from my Asus Zenfone2<br>
Kindly excuse brevity and typos.<o:p></o:p></p>
<div>
<p class="MsoNormal">On 30 Sep 2015 18:15, "Drazek, Keith" <<a href="mailto:kdrazek@verisign.com">kdrazek@verisign.com</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">Thanks Nigel.<br>
<br>
In no particular order, my interpretation of the Board's written comments, what we heard in Los Angeles and from Fadi yesterday is:<br>
<br>
-- Introducing a different governance structure, i.e. membership, is new, untested, and cannot be proven to resist capture in the limited time available to meet the September 2016 date.<br>
-- Shifting authority from the Board to an untested membership body is potentially destabilizing and will be difficult or impossible to sell as not introducing risk at a delicate time.<br>
-- If we're going to shift authority, we must also shift a commensurate level of accountability, and the current SOs and ACs do not have sufficient accountability at this time.<br>
-- ICANN and its SOs/ACs need to be safe from capture from outside and from within; empowering the SOs and ACs without clear safeguards is problematic.<br>
-- Concentrating power in a new "sole membership" body is not balanced if it doesn't include all community members, and two groups (SSAC and RSSAC) have said they want to remain advisory.<br>
-- Shifting from consensus-based decision-making to reliance on a voting structure is not consistent with the multi-stakeholder model.<br>
-- The CCWG recommendation is too complex and difficult to explain/understand, so we need to make smaller, incremental changes that are more easily implemented and understood.<br>
-- A recommendation requiring a substantial governance restructuring will suggest that ICANN is currently broken -- a politically risky message going into the transition.<br>
<br>
I'm obviously not in a position to speak for the Board, but that's my non-legalistic reading of the concerns. I'd be happy to be corrected if my interpretation is off-base.<br>
<br>
That was a reply to your question (a). I can't respond to question (b).<br>
<br>
Regards,<br>
Keith<br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a> [mailto:<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a>] On Behalf
Of Nigel Roberts<br>
Sent: Wednesday, September 30, 2015 12:46 PM<br>
To: <a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a><br>
Subject: Re: [CCWG-ACCT] A way to avoid the 'The Single Member Can Do Anything!' problem<br>
<br>
Let's be Frank, here.<br>
<br>
I'm not entirely unreceptive to the view expressed to me by at least one Board member regarding the idea of a quick win.<br>
<br>
HOWEVER, despite the fairly emphatic nature of the Board's objection to membership model, I do not believe I have read or heard any rationale or reasons for their, apparently unanimous, position.<br>
<br>
Personally I have serious doubts about the Single Member model, although, probably, they are not the same doubts as the Board's.<br>
<br>
But that is the outcome of this WG, and it should not tear up months of work without a rationale. This is simply the IFWP and history repeating itself, otherwise.<br>
<br>
Apparently there is some legal difference of opinion between Sidleys and Jones Day on the technicalities. But I do not beleive that can be the only reason.<br>
<br>
So, can someone please explain, in simply, preferable non legalistic terms why<br>
<br>
(a) the CCWG proposal is unsuitable<br>
(b) the Board's proposal is more suitable.<br>
<br>
<br>
> That said, I'm not confident this would resolve the Board's concerns with membership, so we will need to consider all options available to deliver community empowerment, including variations of the sole designator implementation.<br>
><br>
_______________________________________________<br>
Accountability-Cross-Community mailing list <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" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</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" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><o:p></o:p></p>
</div>
</div>
</body>
</html>