<html><head></head><body><span style="font-family: 'Verdana'; font-size: 13px; color: rgb(102, 102, 102);"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Greetings All,<div><br></div><div>Earlier today Paul Szyndler from auDA sent to RFP3 another alternative proposal (attached).</div><div><br></div><div>I have received a number of questions off list from some ccTLD colleagues and others and thought it might be helpful to address them all in this email to the CWG.</div><div><br></div><div>1. Are there legal issues with the Trust solution? I am not an expert in Californian law but as a lawyer I do know a fair bit about trusts and their structure. The proposal is workable in general terms but there may be nuances of Californian law generally, or specifically as it applies to Californian corporations like ICANN, which would make the proposed structure overly complicated or problematic. Like the 'contract co’ proposal and auDA’s original ‘golden by-law’ proposal I expect this to be put to independent legal experts who can advise on the merits of each of the proposals. </div><div><br></div><div>2. Isn’t creating a trust just creating 'contract co' by another name? No. My understanding of 'contract co’ is that it would be a separate legal entity owned by some, yet to be identified, group of shareholders. With the trust, ICANN would own the IANA function but declare in a legally binding document that it did so on trust for the relevant stakeholder community. And the Guardian of the Trust (see the proposal for details) would control the process by which ICANN could be replaced as trustee in a defined set of circumstances. This is thus an inherently ‘internal to ICANN’ approach.</div><div><br></div><div>3. Why would ICANN be the trustee? In simple terms because auDA believes in an 'internal to ICANN’ approach. We believe that ICANN should run IANA but that there should be the ability to move the IANA function away in certain defined circumstances. That is what this proposal (and our first ‘golden by-law' proposal) achieve and that’s what differentiates them from the ‘contract co’ proposal.</div><div><br></div><div>I know I don’t need to say this but for the avoidance of doubt, this is an auDA proposal. I have not discussed it with my fellow ICANN directors </div><div><br></div><div>I will not be on the RFP3B call Friday as I’ll be somewhere mid-air between Dubai and Melbourne. However, Paul Szyndler will be on the call and will happily enter into any discussion on the proposal and answer (or undertake to get answers to) any questions that may be raised.</div><div><br></div><div>I hope this is helpful.</div><div><br></div><div><span style="color: rgb(66, 66, 66);">Cheers,</span><br><div apple-content-edited="true">
<p class="p3"><br></p>
<p class="p2">Chris Disspain<span class="s1"> </span><span class="s2">|</span><span class="s1"> </span>Chief Executive Officer</p>
<p class="p2">.au Domain Administration Ltd</p>
<p class="p2">T: <span class="s3">+61 3 8341 4111</span><span class="s1"> </span><span class="s2">|</span><span class="s1"> </span>F: <span class="s3">+61 3 8341 4112</span></p>
<p class="p4"><span class="s4">E:</span><span class="s1"> <a href="mailto:ceo@auda.org.au"><span class="s5">ceo@auda.org.au</span></a> </span><span class="s6">|</span><span class="s1"> </span><span class="s4">W:</span><span class="s7"> <a href="http://www.auda.org.au/"><span class="s8">www.auda.org.au</span></a></span><span class="Apple-converted-space"> </span></p>
<p class="p2">auDA – Australia’s Domain Name Administrator</p>
<p class="p5"><br></p>
<p class="p6"><span class="s6"><b>Important Notice</b></span><span class="s1"><b> </b></span><b>- </b>This email may contain information which is confidential and/or subject to legal privilege, and is intended for the use of the named addressee only. If you are not the intended recipient, you must not use, disclose or copy any part of this email. If you have received this email by mistake, please notify the sender and delete this message immediately. Please consider the environment before printing this email.</p>
</div>
<br><div><div></div></div></div></div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><div><div></div></div></div><style type="text/css">
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px}
p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 13.0px Verdana; color: #424242}
p.p3 {margin: 0.0px 0.0px 0.0px 0.0px; font: 13.0px Verdana; color: #424242; min-height: 16.0px}
p.p4 {margin: 0.0px 0.0px 0.0px 0.0px; font: 13.0px Verdana; color: #103ffb}
p.p5 {margin: 0.0px 0.0px 0.0px 0.0px; font: 9.0px Verdana; color: #ffa827; min-height: 11.0px}
p.p6 {margin: 0.0px 0.0px 0.0px 0.0px; font: 10.0px Verdana; color: #424242}
span.s1 {color: #000000}
span.s2 {color: #ff9324}
span.s3 {text-decoration: underline}
span.s4 {color: #424242}
span.s5 {text-decoration: underline ; color: #0000ee}
span.s6 {color: #ffa827}
span.s7 {color: #6c6c6c}
span.s8 {text-decoration: underline ; color: #103ffb}
</style></div></span></body></html>