<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span style="font-family: 'Verdana'; font-size: 13px; color: rgb(102, 102, 102);"><span style="font-family: Verdana; font-size: 13px;" class="">Bruce, Mathieu, All,<div class=""><span style="text-align: justify;" class=""><br class=""></span></div><div class=""><span style="text-align: justify;" class="">The Bylaws to implement the ICG and the CCWG proposal are being drafted and
considered together. The commitment from ICANN has been that the Bylaws
will be adopted to allow for NTIA’s consideration, but the Bylaws will not become EFFECTIVE until the IANA Functions Contract lapses and the stewardship
transition occurs. Given that ICANN cannot require the
transition to occur, the Board, in Marrakech, made clear its commitment that
ICANN would still move forward with the appropriate </span><span style="text-align: justify;" class="">accountability improvements if, for some reason, the transition does not </span><span style="text-align: justify;" class="">occur.</span></div><div class=""><span style="text-align: justify;" class=""><br class=""></span></div><div class="">It might be helpful to refer to the Board’s resolution and rationale from Marrakech. <span class="">In its 10 March 2016 resolution, the
Board said:</span></div><div class=""><p class="MsoNormal"><span class="">"Resolved (2016.03.10.18), the
President and CEO, or his designee, is </span><span class="">directed to plan for the
implementation of the Report so that ICANN is </span><span class="">operationally ready to implement in
the event NTIA approves of the IANA </span><span class="">Stewardship Transition Proposal and
the IANA Functions Contract expires. </span><span class="">The Board is committed to working
with the community to identify the </span><span class="">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."</span></p><p class="MsoNormal" style="text-align:justify;text-justify:inter-ideograph;
mso-pagination:none;mso-layout-grid-align:none;text-autospace:none"><span class="">In its rationale, the Board said:</span></p><p class="MsoNormal"><span class="">"Accepting the Report and
transmitting it to NTIA does not specifically </span><span class="">impose any resource requirements on
ICANN. However, the planning for </span><span class="">implementation that is necessary to
be in place for ICANN to be ready to </span><span class="">implement these changes when
appropriate requires significant resources, including amending
ICANN’s Bylaws, supporting the revisions to the Independent Review Process,
confirming that processes are in place for the community escalation processes,
and other planning as required. The implementation planning for the entirety of
the IANA Stewardship Transition Process is a coordinated effort, with the
interrelated operational and accountability requirements within the ICG¹s
Proposal and the CCWG-Accountability¹s Report considered
together. Given that there is the possibility that NTIA may not be
able to approve ICG’s Proposal, if that determination is made, the Board is
committed to work with the community to implement those parts of the
CCWG-Accountability Report that do not interfere with the obligations ICANN
would maintain under an IANA Functions Contract with NTIA."</span></p><p class="MsoNormal"><span class="">The CCWG report, while separate, has
dependencies on the ICG proposal. </span><span class="">The bylaws terms are linked - and
ICANN has committed to work with the </span><span class="">community to unlink those terms if it
is ever needed.</span></p><p class="MsoNormal"><span class="">On a practical matter, there is a
need to do implementation work to allow </span><span class="">for the mechanisms in the new Bylaws
to work, so the anticipation that the Bylaws will not be in effect until 1
October puts a far more realistic </span><span class="">deadline into place to allow for
those implementation efforts to conclude. </span><span class="">For example, the procedural rules
around the IRP and the identification </span><span class="">of a provider (which is needed before
a standing panel is in place) cannot </span><span class="">be completed by a May 27 Bylaws
approval date.</span></p><div class=""><br class=""></div><div class="">Hope this helps.</div>
<!--EndFragment--></div><div class=""><br class=""></div><div class=""><div class=""><p class="p1" style="margin: 0px; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-family: Helvetica; min-height: 14px; color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br class=""></p><p class="p2" style="color: rgb(148, 67, 251); margin: 0px; font-style: normal; font-variant: normal; font-weight: normal; font-size: 13px; line-height: normal; font-family: Verdana; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Cheers,</p><p class="p3" style="color: rgb(148, 67, 251); margin: 0px; font-style: normal; font-variant: normal; font-weight: normal; font-size: 13px; line-height: normal; font-family: Verdana; min-height: 16px; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br class=""></p><p class="p2" style="color: rgb(148, 67, 251); margin: 0px; font-style: normal; font-variant: normal; font-weight: normal; font-size: 13px; line-height: normal; font-family: Verdana; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Chris</p>
</div>
<br class=""><div style="color: rgb(102, 102, 102);" class=""><blockquote type="cite" class=""><div class="">On 14 Apr 2016, at 19:56 , Bruce Tonkin via bylaws-coord <<a href="mailto:bylaws-coord@icann.org" class="">bylaws-coord@icann.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hello All,<br class=""><br class=""><blockquote type="cite" class=""><blockquote type="cite" class=""> Finally, a statement in Akram’s blog struck me as a shift from our previous discussions. The blog states “The Bylaws will only become effective upon the successful completion of the transition.” I was under the impression in Marrakech that only the subset of Bylaws that are related to the IANA contract expiring would see its effectiveness delayed until the transition. I would appreciate clarification here whether this intent has changes, and what is the rationale. <br class=""></blockquote></blockquote><br class=""><br class="">I have discussed this further with Akram Atallah in his role as Acting CEO of ICANN.<br class=""><br class="">As the Board stated in Marrakech - at a principle level the Board intends to proceed with the improvements to the accountability that have been submitted to the NTIA for review. With respect to the improvements in the management of the IANA function - there is a dependency that some of these changes can’t take effect until the NTIA formally agrees to let the existing NTIA contract with ICANN lapse.<br class=""><br class="">With respect to agreements with external parties - those agreements can have "conditions precedent" clauses that describe the events that must occur before terms in the new agreement take effect.<br class=""><br class="">When ICANN did its last major rewrite of the Bylaws a "Transition Article" (Article XX of the current bylaws) was established to map out the steps to transition to the new bylaws.<br class=""><br class="">In an ideal world we would have a section of bylaws that can take effect immediately after Board approval in June/July, and a section of bylaws that may take effect after the NTIA agreement with ICANN lapses. <br class=""><br class="">The reality is that we are creating a single draft of the bylaws that combine all the changes resulting from the work in the ICG and CCWG on Accountability, assuming that the NTIA will agree to the transition and let the existing agreement lapse in September 2016. There is no clean separation of clauses that are directly dependent on the IANA transition.<br class=""><br class="">I request that the combined legal team (John, Holly, Rosemary and their colleagues) provide us with some advice on how the bylaws that the Board is asked to approve in June/July can account for:<br class=""><br class="">- possible different timing when some parts of the new bylaws come into effect<br class=""><br class="">- a scenario where the NTIA chooses not to let the current NTIA agreement lapse, and chooses to either extend the existing agreement or alter the existing agreement in some way.<br class=""><br class="">Regards,<br class="">Bruce Tonkin<br class=""><br class=""><br class="">_______________________________________________<br class="">bylaws-coord mailing list<br class=""><a href="mailto:bylaws-coord@icann.org" class="">bylaws-coord@icann.org</a><br class=""><a href="https://mm.icann.org/mailman/listinfo/bylaws-coord" class="">https://mm.icann.org/mailman/listinfo/bylaws-coord</a><br class=""></div></div></blockquote></div><br class=""></div></span></span></body></html>