<p dir="ltr">Sent from my LG G4<br>
Kindly excuse brevity and typos<br>
On 27 May 2016 10:24 p.m., &quot;Phil Corwin&quot; &lt;<a href="mailto:psc@vlaw-dc.com">psc@vlaw-dc.com</a>&gt; wrote:<br>
&gt;<br>
&gt; I&#39;m having difficulty identifying a single new accountability measure that can&#39;t be implemented in the absence of the IANA transition. <br>
&gt;<br>
SO: Really? I don&#39;t think one needs to read far to see that; perhaps I should remind that the bylaw update included the recognition/implementation of proposals from the 3OC. Anyway let&#39;s not start that discussion for now, let&#39;s enjoy the moment and feel accomplished. ;-)</p>
<p dir="ltr">Regards <br></p>
<p dir="ltr">&gt; I hesitate to rain on the parade on what is a very important and overall positive development for the ICANN community, and I&#39;m not advocating that the accountability improvements take effect before October 1. But these are needed improvements on which the community demonstrated strong consensus support.<br>
&gt;<br>
&gt; Regards, Philip<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Philip S. Corwin, Founding Principal<br>
&gt; Virtualaw LLC<br>
&gt; 1155 F Street, NW<br>
&gt; Suite 1050<br>
&gt; Washington, DC 20004<br>
&gt; 202-559-8597/Direct<br>
&gt; 202-559-8750/Fax<br>
&gt; 202-255-6172/Cell<br>
&gt;<br>
&gt; Twitter: @VlawDC<br>
&gt;  <br>
&gt; &quot;Luck is the residue of design&quot; -- Branch Rickey<br>
&gt;<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; 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 Samantha Eisner<br>
&gt; Sent: Friday, May 27, 2016 3:02 PM<br>
&gt; To: avri doria; <a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a><br>
&gt; Subject: Re: [CCWG-ACCT] New ICANN Bylaws<br>
&gt;<br>
&gt; Hi Avri,<br>
&gt;<br>
&gt; Here is the language from the Resolution on the effective date:<br>
&gt;<br>
&gt; &quot;Resolved (2016.05.27.02), the New ICANN Bylaws will be deemed effective upon the expiration the IANA Functions Contract between ICANN and NTIA.<br>
&gt; The Board reaffirms its Resolution 2016.03.10.18, stating, &#39;The Board is committed to working with the community to identify the portions of the CCWG-Accountability recommendations that can be implemented in the event that it is determined that ICANN&#39;s obligations to perform the IANA Functions will remain under contract with NTIA.¹&quot;<br>
&gt;<br>
&gt;<br>
&gt; Best regards,<br>
&gt;<br>
&gt; Sam<br>
&gt;<br>
&gt; On 5/27/16, 11:51 AM, &quot;<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a> on behalf of avri doria&quot; &lt;<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a> on behalf of <a href="mailto:avri@apc.org">avri@apc.org</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt;Hi,<br>
&gt; &gt;<br>
&gt; &gt;anyone know when they go into effect?<br>
&gt; &gt;<br>
&gt; &gt;immediately?<br>
&gt; &gt;<br>
&gt; &gt;avri<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;On 27-May-16 14:44, Hillary Jett wrote:<br>
&gt; &gt;&gt; Original link: <a href="https://www.icann.org/news/blog/new-icann-bylaws">https://www.icann.org/news/blog/new-icann-bylaws</a><br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;   New ICANN Bylaws<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; *Author: Steve Crocker*<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Today, on behalf of the ICANN Board, I am pleased to announce the<br>
&gt; &gt;&gt; adoption<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&lt;<a href="http://www.icann.org/resources/board-material/resolutions-2016-05-27-">http://www.icann.org/resources/board-material/resolutions-2016-05-27-</a><br>
&gt; &gt;&gt;en&gt;<br>
&gt; &gt;&gt; of<br>
&gt; &gt;&gt; the new ICANN Bylaws<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&lt;<a href="https://www.icann.org/en/system/files/files/adopted-bylaws-27may16-en">https://www.icann.org/en/system/files/files/adopted-bylaws-27may16-en</a><br>
&gt; &gt;&gt;.pd<br>
&gt; &gt;&gt;f&gt;,<br>
&gt; &gt;&gt; which reflect changes made as a result of the IANA Stewardship<br>
&gt; &gt;&gt; Transition package of proposals<br>
&gt; &gt;&gt; &lt;<a href="https://www.icann.org/stewardship-accountability">https://www.icann.org/stewardship-accountability</a>&gt;. The new Bylaws<br>
&gt; &gt;&gt; are the result of hundreds of hours of work by the community and the<br>
&gt; &gt;&gt; legal teams. The Regional Internet Registries Service Level Agreement<br>
&gt; &gt;&gt; and Internet Engineering Task Force Memorandum of Understanding<br>
&gt; &gt;&gt; Supplemental Agreement have also been approved for signing and will<br>
&gt; &gt;&gt; go into effect after the transition.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Later today, ICANN will be transmitting the new Bylaws to the U.S.<br>
&gt; &gt;&gt; Department of Commerce¹s National Telecommunications and Information<br>
&gt; &gt;&gt; Administration (NTIA). NTIA has previously stated that adoption of<br>
&gt; &gt;&gt; the new Bylaws is required for them to complete their review of the<br>
&gt; &gt;&gt; proposals, which is expected to occur in June.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; This is an important milestone for ICANN and the community. As we<br>
&gt; &gt;&gt; await the release of NTIA¹s report, we continue to prepare for<br>
&gt; &gt;&gt; implementation of the transition proposals. We thank everyone for<br>
&gt; &gt;&gt; their continued hard work and support during this transition process.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; --<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Hillary Jett<br>
&gt; &gt;&gt; Communications Coordinator<br>
&gt; &gt;&gt; Internet Corporation for Assigned Names and Numbers (ICANN)<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Mobile: +1 (202) 674-3403<br>
&gt; &gt;&gt; Email: <a href="mailto:hillary.jett@icann.org">hillary.jett@icann.org</a><br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; _______________________________________________<br>
&gt; &gt;&gt; Accountability-Cross-Community mailing list<br>
&gt; &gt;&gt; <a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
&gt; &gt;&gt; <a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;---<br>
&gt; &gt;This email has been checked for viruses by Avast antivirus software.<br>
&gt; &gt;<a href="https://www.avast.com/antivirus">https://www.avast.com/antivirus</a><br>
&gt; &gt;<br>
&gt; &gt;_______________________________________________<br>
&gt; &gt;Accountability-Cross-Community mailing list<br>
&gt; &gt;<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
&gt; &gt;<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; Accountability-Cross-Community mailing list <a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
&gt; <a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
&gt;<br>
&gt; -----<br>
&gt; No virus found in this message.<br>
&gt; Checked by AVG - <a href="http://www.avg.com">www.avg.com</a><br>
&gt; Version: 2016.0.7497 / Virus Database: 4568/12262 - Release Date: 05/19/16 Internal Virus Database is out of date.<br>
&gt; _______________________________________________<br>
&gt; Accountability-Cross-Community mailing list<br>
&gt; <a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
&gt; <a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
</p>