<div dir="ltr">I agree with what Chuck has to say. We should deliberate on all options before we decide. <div><br></div><div>Please do suggest other options so that we can discuss them as well.<div><br></div><div>Thanks,</div><div>Acharya</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 16, 2014 at 3:13 AM, Gomes, Chuck <span dir="ltr"><<a href="mailto:cgomes@verisign.com" target="_blank">cgomes@verisign.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Forgive me for being slow but it is not obvious to me that option 1 makes sense, i.e., ‘</span>create a new legal entity<span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">’.
I see it as one option, but before we decide it is the best option we should explore as many options as possible. Even if we eliminate the other options mentioned below, we should not assume that we have considered all possible options.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Chuck<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<div>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<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""> <a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">cwg-stewardship-bounces@icann.org</a> [mailto:<a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">cwg-stewardship-bounces@icann.org</a>]
<b>On Behalf Of </b>Krishna Seeburn<br>
<b>Sent:</b> Wednesday, October 15, 2014 5:30 PM<br>
<b>To:</b> Guru Acharya<br>
<b>Cc:</b> <a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a><br>
<b>Subject:</b> Re: [CWG-Stewardship] Names Community vs the other two communities<u></u><u></u></span></p>
</div>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Thanks for those acharya.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">IETF and the RIRs were already working in that direction from the very start and even before the official formal announcement from icann / ntia. These were already talks and were well ahead of anything. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">The option 1 makes sense and in fact i am wondering how much more talks we will have before we can decide on what is more than obvious.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">The names community however have a different but more challenging approach. As much as we are technical but we have a different impact on the community. Our challenges are way different for sure. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">But good thinking .., perhaps yes a good way forward. But a consensus in way forward is what matters and we all need to agree and that is the bigger challenge. In whatever we come up with we will need a mid platform to agree with everyone
to some point.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">My 2 cents<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><br>
<i>Kris Seeburn</i><u></u><u></u></p>
<div>
<p class="MsoNormal">skype: kris_seeburn30<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Linkedin:<a href="http://mu.linkedin.com/in/kseeburn" target="_blank">mu.linkedin.com/in/kseeburn</a><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On Oct 16, 2014, at 1:10 AM, Guru Acharya <<a href="mailto:gurcharya@gmail.com" target="_blank">gurcharya@gmail.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal">How the names community approach will differ from the approach adopted by the numbers community and protocols community?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Numbers Community: APNIC has reached consensus on its proposal. According to the proposal, IANA will continue to reside in ICANN. It proposes to replace NTIA oversight with a Service Level Agreement (SLA) and Affirmation of Commitment (AOC)
between NRO and ICANN.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><a href="http://www.slideshare.net/fullscreen/apnic/report-ianatransition/1" target="_blank">www.slideshare.net/fullscreen/apnic/report-ianatransition/1</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Protocols Community: The IETF draft proposal suggests that no structural changes are required as a result of the transition. The MOU between ICANN and the IETF community will continue to govern the existing relationship. Again, IANA will
continue to reside in ICANN.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><a href="http://tools.ietf.org/html/draft-ietf-ianaplan-icg-response-00" target="_blank">http://tools.ietf.org/html/draft-ietf-ianaplan-icg-response-00</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Therefore, neither the numbers community, nor the protocol community appear to be in the direction of suggesting a new MS Oversight Entity to replace NTIA and its oversight. Merely contracts between existing entities will be updated to
replace NTIA oversight.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Can the names community adopt a similar approach? Can a contractual agreement (SLA/AOC/MOU) between ICANN and GNSO/CCNSO be expected to replace NTIA oversight?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Clearly NO! This approach can not be adopted by the names community because the names community resides within ICANN, which is also the IANA operator. Specifically, GNSO and CCNSO are essentially subsets of ICANN, and therefore a contractual
agreement (SLA/AOC/MOU) between ICANN and GNSO/CCNSO can not be expected to replace NTIA oversight.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Therefore, it is essential to either<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Option (i): create a new legal entity, which has a contractual oversight relationship with ICANN. This would be similar to <a href="http://www.internetgovernance.org/2014/08/04/students-school-faculty-on-iana-transition-the-meissen-proposal/" target="_blank">http://www.internetgovernance.org/2014/08/04/students-school-faculty-on-iana-transition-the-meissen-proposal/</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Option (ii): expect ICANN to self-regulate<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Option (iii): make a new legal entity comprising of CCNSO and GNSO that is structurally independent of ICANN and require that new entity to enter into a contractual oversight agreement (SLA/AOC/MOU) with ICANN.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">From the above three options, clearly option (ii) is not acceptable because of the lack of trust in the ICANN enhanced accountability process.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I also feel that option (iii) is not feasible because the CCNSO and GNSO are heavily integrated with ICANN and structural separation of these two communities from ICANN will be in-feasible.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Also, from the Jordan Carter document, the option on page 7 can be discarded, which makes ICANN the oversight body, as IANA will continue to reside in ICANN, as clearly suggested by the proposals of the protocols and numbers community.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Therefore, option (i) is clearly the only option available with the names community.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Regards,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Acharya<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><u></u><u></u></p>
</div>
</blockquote>
</div></div></div>
</div>
</blockquote></div><br></div>