<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>As we have said all along we are planning for the future not relying on the past. We need to make sure that our bylaws are suitable for the next 18 years of ICANN.</div>
<div>Lets not get caught up in looking for examples from the past and focus on lowering the potential risk in the future. The problem is that examples are always going to be subjective based on the proponent and their stance. I think we need to accept that
 a majority of the community feels that there is a potential risk that needs mitigation, the work we should be doing is working out the best way to implement that mitigation rather than going back and forth on examples.</div>
<div><br>
</div>
<div>If we can’t come to agreement on alternative wording then we have to default back to the existing text that was in the 2nd draft report.</div>
<div><br>
</div>
<div>-jg</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>&lt;<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a>&gt; on behalf of Seun Ojedeji &lt;<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>&gt;<br>
<span style="font-weight:bold">Date: </span>Sunday 22 November 2015 at 1:55 p.m.<br>
<span style="font-weight:bold">To: </span>Paul Rosenzweig &lt;<a href="mailto:paul.rosenzweig@redbranchconsulting.com">paul.rosenzweig@redbranchconsulting.com</a>&gt;<br>
<span style="font-weight:bold">Cc: </span>&quot;<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>&quot; &lt;<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>&gt;<br>
<span style="font-weight:bold">Subject: </span>Re: [CCWG-ACCT] Board comments on the Mission statement)<br>
</div>
<div><br>
</div>
<div>
<div>
<p dir="ltr">Hi,</p>
<p dir="ltr">A lot has been said, there has been examples and counter examples as well. Could you share at least one example that has survived being countered and most importantly a mission wording that will adequately address that example.</p>
<p dir="ltr">Thanks</p>
<p dir="ltr">Sent from my Asus Zenfone2<br>
Kindly excuse brevity and typos.</p>
<div class="gmail_quote">On 22 Nov 2015 00:42, &quot;Paul Rosenzweig&quot; &lt;<a href="mailto:paul.rosenzweig@redbranchconsulting.com">paul.rosenzweig@redbranchconsulting.com</a>&gt; wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<p style="margin-top:0px" dir="ltr">Yes but there have been many such examples already e.g. Melton 5 minutes ago.&nbsp; We are already in the drafting.&nbsp; So this seems a bit retrograde mo?</p>
<p dir="ltr">--<br>
Paul<br>
Sent from myMail app for Android</p>
Saturday, 21 November 2015, 05:13PM -06:00 from Bruce Tonkin &lt;<a href="mailto:Bruce.Tonkin@melbourneit.com.au" target="_blank">Bruce.Tonkin@melbourneit.com.au</a>&gt;:<br>
<br>
<blockquote style="border-left:1px solid #fc2c38;margin:0px 0px 0px 10px;padding:0px 0px 0px 10px" cite="http://14481476630000085528">
<div>
<div>
<div>Hello Paul,<br>
<br>
<div>&gt;&gt; &nbsp; I read the concerns about the restriction clause as suggesting that it be deleted (perhaps I am wrong in this)
<br>
</div>
<br>
No- we didn’t say that a restriction clause should be deleted. <br>
<br>
We said:<br>
<br>
&quot; The Board asks that the CCWG provide some examples of what the<br>
CCWG believes that ICANN should and should not be able to do.<br>
That information can then be provided to counsel to see if text can be<br>
drafted to address the broader concerns.&quot;<br>
<br>
<br>
Regards,<br>
Bruce Tonkin<br>
<br>
<br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="https://e-aj.my.com/compose?To=Accountability%2dCross%2dCommunity@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><br>
</div>
</div>
</div>
</blockquote>
</div>
<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" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br>
</blockquote>
</div>
</div>
</div>
</span>
</body>
</html>