<p dir="ltr">Hello,</p>
<p dir="ltr">Here is the current ICANN mission.</p>
<p dir="ltr"><b>Section 1. MISSION</b></p>
<p dir="ltr">The mission of The Internet Corporation for Assigned Names and Numbers ("ICANN") is to coordinate, at the overall level, the global Internet's systems of unique identifiers, and in particular to ensure the stable and secure operation of the Internet's unique identifier systems. In particular, ICANN:</p>
<blockquote><p dir="ltr">1. Coordinates the allocation and assignment of the three sets of unique identifiers for the Internet, which are</p>
</blockquote>
<blockquote><blockquote><p dir="ltr">a. Domain names (forming a system referred to as "DNS");</p>
<p dir="ltr">b. Internet protocol ("IP") addresses and autonomous system ("AS") numbers; and</p>
<p dir="ltr">c. Protocol port and parameter numbers.<br>
</p>
</blockquote>
</blockquote>
<blockquote><p dir="ltr"><br>
2. Coordinates the operation and evolution of the DNS root name server system.</p>
<p dir="ltr">3. Coordinates policy development reasonably and appropriately related to these technical functions.<br>
</p>
</blockquote>
<p dir="ltr"><br>
Could you kindly provide what the full newly proposed mission statement look like. As it's looking like we are about developing a full page mission statement.</p>
<p dir="ltr">Regards<br>
Sent from my Asus Zenfone2<br>
Kindly excuse brevity and typos.</p>
<div class="gmail_quote">On 10 Nov 2015 23:58, "Burr, Becky" <<a href="mailto:Becky.Burr@neustar.biz">Becky.Burr@neustar.biz</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<span style="font-family:'Avenir Next';font-size:12pt">Please read all the way through to the bottom for a question and proposal.</span></div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<span style="font-family:'Avenir Next';font-size:12pt"><br>
</span></div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<span style="font-family:'Avenir Next';font-size:12pt">Based on our discussion this morning, I believe that the following statements reflect the consensus of the CCWG (lack of </span><span style="font-family:'Avenir Next';font-size:12pt">“</span><span style="font-family:'Avenir Next';font-size:12pt">full
consensus” on 1 point noted in text):</span></div>
<div>
<div>
<p class="MsoNormal" style="color:rgb(0,0,0)"><font face="Avenir Next"> </font></p>
<p><font face="Avenir Next"><span style="color:rgb(0,0,0)">· </span><span style="color:rgb(0,0,0)">ICANN’s Mission with respect to names is described in the
Mission Statement as follows: </span>With respect to NAMES, ICANN’s Mission is to coordinate the allocation and assignment of names in the root zone of the Domain Name System ("DNS"). In this role, ICANN’s Mission is to coordinate the development and implementation
of policies: (I)<span style="color:rgb(0,0,0)">For which uniform or coordinated resolution is reasonably necessary to facilitate the openness, interoperability, resilience, security and/or stability of the DNS; and (ii) </span><span style="color:rgb(0,0,0)">That
are developed through a bottom-up, consensus-based multi- stakeholder process and designed to ensure the stable and secure operation of the Internet’s unique names systems.</span></font></p>
<p style="color:rgb(0,0,0)">
<font face="Avenir Next">· ICANN’s Mission is limited and enumerated.<u></u><u></u></font></p>
<p style="color:rgb(0,0,0)">
<font face="Avenir Next">· ICANN’s should act in accordance with, and only as reasonably appropriate to achieve its Mission.<u></u><u></u></font></p>
<p style="color:rgb(0,0,0)">
<font face="Avenir Next">· Coordinating development, implementation, and enforcement of Consensus Policy, as defined by Specification 1 of the New gTLD Registry Agreement and Specification 4 of the 2013 Registrar Accreditation Agreement,
is within ICANN’s Mission.<u></u><u></u></font></p>
<p style="color:rgb(0,0,0)">
<font face="Avenir Next">· ICANN should have the authority to enforce agreements with contracted parties, subject to established means of community input on those agreements and reasonable checks and balances on its ability to impose
obligations exceeding ICANN’s Mission on such parties.<u></u><u></u></font></p>
<p style="color:rgb(0,0,0);margin-left:1in">
<font face="Avenir Next">o To the extent that registry operators voluntarily assume obligations with respect to registry operations as part of the application process, ICANN should have the authority to enforce those
commitments. <u></u><u></u></font></p>
<p style="color:rgb(0,0,0);margin-left:1.5in">
<font face="Avenir Next"> <i>NOTE: There is not “full consensus” on this position</i>.<u></u><u></u></font></p>
<p style="color:rgb(0,0,0);margin-left:1in">
<font face="Avenir Next">o In general, consistent with ordinary contract concepts, registries and registrars should be presumed to have agreed to the terms and conditions of any contract with ICANN. </font></p>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<p style="color:rgb(0,0,0);margin-left:1in">
<i style="font-family:'Avenir Next'">That said</i><span style="font-family:'Avenir Next'">, there should be some mechanism whereby contracted parties can enter into such agreements without waiving their rights to challenge specified provisions of such an
agreement on the grounds that they exceed the scope of ICANN’s Mission.</span><span style="font-family:'Avenir Next'"> Any such mechanism would have to provide adequate notice, needs to be developed, etc.</span></p>
</blockquote>
<div>
<p style="color:rgb(0,0,0);margin-left:1in">
<span style="font-family:'Avenir Next'"><br>
</span></p>
<p style="color:rgb(0,0,0);margin-left:1in">
<span style="font-family:'Avenir Next'"><b>We do not appear to have consensus on the following concept</b>: </span><i style="font-size:12pt;font-family:'Avenir Next'"><span style="color:rgb(51,102,255)">Without in any way limiting
the foregoing absolute prohibition, ICANN shall not regulate services that use the Internet's unique identifiers, or the content that such services carry or provide.</span></i></p>
<p style="color:rgb(0,0,0);margin-left:1in">
<span style="font-size:12pt;font-family:'Avenir Next'"><br>
</span></p>
<p style="margin-left:1in">
<span style="color:rgb(0,0,0);font-size:12pt;font-family:'Avenir Next'"><i><b>Question</b>: Does the following formulation t</i></span><span style="font-family:'Avenir Next'">hread the needle between those who say that ICANN
should not use its contracting authority to regulate registrant behavior and those who point out that the Registrar Accreditation Agreement, for example, requires registrants to provide accurate and up-to-date WHOIS data: <i><font color="#0000ff">I</font></i></span><span style="font-family:'Avenir Next';font-size:12pt"><i><font color="#0000ff">CANN
should not use its authority to enter into contracts with registries and registrars to impose obligations and limitations on registrants with respect to issues that are not properly the subject of Consensus Policy.</font></i></span></p>
</div>
<span style="font-size:16px"><br>
</span></div>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div><span style="font-size:16px;white-space:pre-wrap"></span><b style="font-size:16px"><i>PROPOSAL</i></b><span style="font-size:16px">: If so, I propose that the CCWG provide the text above as guidance for the final bylaws drafters
in interpreting the admonition that "</span><span style="font-size:16px;font-family:'Avenir Book'">ICANN shall act
</span><span style="font-size:16px;font-family:'Avenir Book';color:rgb(0,0,144)">strictly
</span><span style="font-size:16px;font-family:'Avenir Book'">in accordance with, and
</span><span style="font-size:16px;font-family:'Avenir Book';color:rgb(0,0,144)">only</span><font face="Avenir Book" style="font-size:16px"> as reasonably appropriate to achieve its Mission.</font><font face="Avenir Book" style="font-size:16px">”</font><font face="Avenir Book"><span style="font-size:16px"> I
believe this would (1) eliminate concerns and ambiguity regarding use of the word “regulation,”; (2) reflect consensus on the principles; and (3) address the late change/legislative history/statutory construction concern raised by Paul R. and others.</span></font></div>
<div><span style="font-size:16px"> </span></div>
</blockquote>
<p class="MsoNormal" style="color:rgb(0,0,0);font-family:Calibri,sans-serif;margin-top:12pt">
</p>
<p class="MsoNormal" style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px;margin-top:12pt">
<b><span style="font-size:9pt;line-height:115%">J. Beckwith Burr</span></b><b><span style="font-size:10.0pt;line-height:115%;color:#262626">
</span></b><b><span style="font-size:9.0pt;line-height:115%;color:#3366ff"><br>
</span></b><b><span style="font-size:9.0pt;line-height:115%;color:#008656">Neustar, Inc.</span></b><b><span style="font-size:9.0pt;line-height:115%;color:#068658">
</span></b><span style="font-size:9.0pt;line-height:115%;color:#7d7d7d">/</span><b><span style="font-size:9.0pt;line-height:115%;color:#068658">
</span></b><span style="font-size:9.0pt;line-height:115%;color:#7d7d7d">Deputy General Counsel & Chief Privacy Officer<br>
1775 Pennsylvania Avenue NW, Washington D.C. 20006</span><span style="font-size:9.0pt;line-height:115%;color:gray"><br>
</span><b><span style="font-size:9.0pt;line-height:115%;color:#008656">Office:</span></b><b><span style="font-size:9.0pt;line-height:115%;color:#7d7d7d">
</span></b><span style="font-size:9.0pt;line-height:115%;color:#7d7d7d"><a href="tel:%2B1.202.533.2932" value="+12025332932" target="_blank">+1.202.533.2932</a>
</span><b><span style="font-size:9.0pt;line-height:115%;color:#008656">Mobile:</span></b><b><span style="font-size:9.0pt;line-height:115%;color:#7d7d7d">
</span></b><span style="font-size:9.0pt;line-height:115%;color:#7d7d7d"><a href="tel:%2B1.202.352.6367" value="+12023526367" target="_blank">+1.202.352.6367</a>
<strong><span style="font-family:Arial">/</span></strong></span><span style="font-size:9.0pt;line-height:115%;color:#068658">
</span><a href="http://www.neustar.biz" target="_blank"><b><span style="font-size:9.0pt;line-height:115%;color:#008656">neustar.biz</span></b></a><span style="font-size:9.0pt;line-height:115%;color:gray"><u></u><u></u></span></p>
</div>
</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>