<html>
<body>
<blockquote type=cite class=cite cite="">On 27 May 2016 10:24 p.m.,
"Phil Corwin"
<<a href="mailto:psc@vlaw-dc.com">psc@vlaw-dc.com</a>> wrote:<br>
><br>
> I'm having difficulty identifying a single new accountability
measure that can't be implemented in the absence of the IANA transition.
</blockquote><br>
Seun Ojedeji wrote:<br>
<blockquote type=cite class=cite cite="">><br>
Really? I don'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's not start that discussion for now,
let's enjoy the moment and feel accomplished. ;-)<br>
</blockquote><br>
I agree with Phil on this - why shouldn't the Board commit to implement
the accountability measures whatever does or doesn't happen on October
1? Everyone has been saying all along that there's an
"accountability deficit" in ICANN's current structure; the CCWG
has come up with a proposal, endorsed by the Board, to remedy some/all of
those existing deficiencies to make the institution more accountable; why
should implementation of those revisions be dependent on the status of
the IANA Functions Contract? To an outsider, this looks a little
bit like the Board saying: unless you turn over all the marbles to us,
we're not going to do the things we need to do to make the institution
more accountable to the community, as though "accountability"
were some sort of quid pro quo for the transfer of control over the IANA
resources. That would be a rather strange position for the Board to
be taking - <br><br>
David<br><br>
<br><br>
<blockquote type=cite class=cite cite="">> -----Original
Message-----<br>
> From:
<a href="mailto:accountability-cross-community-bounces@icann.org">
accountability-cross-community-bounces@icann.org</a>
[<a href="mailto:accountability-cross-community-bounces@icann.org" eudora="autourl">
mailto:accountability-cross-community-bounces@icann.org</a>] On Behalf Of
Samantha Eisner<br>
> Sent: Friday, May 27, 2016 3:02 PM<br>
> To: avri doria;
<a href="mailto:accountability-cross-community@icann.org">
accountability-cross-community@icann.org</a><br>
> Subject: Re: [CCWG-ACCT] New ICANN Bylaws<br>
><br>
> Hi Avri,<br>
><br>
> Here is the language from the Resolution on the effective date:<br>
><br>
> "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>
> The Board reaffirms its Resolution 2016.03.10.18, stating, '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's obligations to perform the IANA
Functions will remain under contract with NTIA.¹"<br>
><br>
><br>
> Best regards,<br>
><br>
> Sam<br>
><br>
> On 5/27/16, 11:51 AM,
"<a href="mailto:accountability-cross-community-bounces@icann.org">
accountability-cross-community-bounces@icann.org</a> on behalf of avri
doria"
<<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>> wrote:<br>
><br>
> >Hi,<br>
> ><br>
> >anyone know when they go into effect?<br>
> ><br>
> >immediately?<br>
> ><br>
> >avri<br>
> ><br>
> ><br>
> >On 27-May-16 14:44, Hillary Jett wrote:<br>
> >> Original link:
<a href="https://www.icann.org/news/blog/new-icann-bylaws">
https://www.icann.org/news/blog/new-icann-bylaws</a><br>
> >><br>
> >><br>
> >>Â Â New ICANN Bylaws<br>
> >><br>
> >> *Author: Steve Crocker*<br>
> >><br>
> >> Today, on behalf of the ICANN Board, I am pleased to
announce the<br>
> >> adoption<br>
> >><br>
>
>><<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>
> >>en><br>
> >> of<br>
> >> the new ICANN Bylaws<br>
> >><br>
>
>><<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>
> >>.pd<br>
> >>f>,<br>
> >> which reflect changes made as a result of the IANA
Stewardship<br>
> >> Transition package of proposals<br>
> >>
<<a href="https://www.icann.org/stewardship-accountability">
https://www.icann.org/stewardship-accountability</a>>. The new
Bylaws<br>
> >> are the result of hundreds of hours of work by the
community and the<br>
> >> legal teams. The Regional Internet Registries Service Level
Agreement<br>
> >> and Internet Engineering Task Force Memorandum of
Understanding<br>
> >> Supplemental Agreement have also been approved for signing
and will<br>
> >> go into effect after the transition.<br>
> >><br>
> >> Later today, ICANN will be transmitting the new Bylaws to
the U.S.<br>
> >> Department of Commerce¹s National Telecommunications and
Information<br>
> >> Administration (NTIA). NTIA has previously stated that
adoption of<br>
> >> the new Bylaws is required for them to complete their
review of the<br>
> >> proposals, which is expected to occur in June.<br>
> >><br>
> >> This is an important milestone for ICANN and the community.
As we<br>
> >> await the release of NTIA¹s report, we continue to prepare
for<br>
> >> implementation of the transition proposals. We thank
everyone for<br>
> >> their continued hard work and support during this
transition process.<br>
> >><br>
> >> --<br>
> >><br>
> >> Hillary Jett<br>
> >> Communications Coordinator<br>
> >> Internet Corporation for Assigned Names and Numbers
(ICANN)<br>
> >><br>
> >> Mobile: +1 (202) 674-3403<br>
> >> Email:
<a href="mailto:hillary.jett@icann.org">hillary.jett@icann.org</a><br>
> >><br>
> >><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" eudora="autourl">
https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
<br>
> ><br>
> ><br>
> >---<br>
> >This email has been checked for viruses by Avast antivirus
software.<br>
>
><a href="https://www.avast.com/antivirus">
https://www.avast.com/antivirus</a><br>
> ><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" eudora="autourl">
https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
<br>
><br>
> _______________________________________________<br>
> Accountability-Cross-Community mailing list
<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" eudora="autourl">
https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
<br>
><br>
> -----<br>
> No virus found in this message.<br>
> Checked by AVG - <a href="http://www.avg.com">www.avg.com</a><br>
> Version: 2016.0.7497 / Virus Database: 4568/12262 - Release Date:
05/19/16 Internal Virus Database is out of date.<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" eudora="autourl">
https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
<br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
Accountability-Cross-Community@icann.org<br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" eudora="autourl">
https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</blockquote><br>
*******************************<br>
<font size=2>David G. Post<br>
Volokh Conspiracy Blog
<a href="http://www.washingtonpost.com/people/david-post" eudora="autourl">
http://www.washingtonpost.com/people/david-post</a> <br>
Book (ISO Jefferson's Moose)
<a href="http://tinyurl.com/c327w2n%A0%A0%A0%A0" eudora="autourl">
http://tinyurl.com/c327w2n </a> <br>
Music
<a href="https://soundcloud.com/davidpost-1/sets" eudora="autourl">
https://soundcloud.com/davidpost-1/sets<br>
</a>Publications & Misc.
<a href="http://www.ssrn.com/author=537%A0%A0" eudora="autourl">
http://www.ssrn.com/author=537 </a>
<a href="http://www.davidpost.com/" eudora="autourl">
http://www.davidpost.com</a> <br>
</font>******************************* </body>
</html>