<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Mathieu,<div><br></div><div>Thanks. I will work with the board and staff to figure out how best to expand the indicated process to include the formal approval and adoption process. We will get back to you.</div><div><br></div><div>Steve<br><div><br></div><div><br><div><div>On Jul 8, 2015, at 2:27 AM, Mathieu Weill <<a href="mailto:mathieu.weill@afnic.fr">mathieu.weill@afnic.fr</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000">
Dear Steve, <br>
<br>
I think the process described was not capturing the final steps
which would lead to Board approval of the Bylaws. We stopped where
we thought our remit stopped. <br>
<br>
I expect that an addition of these extra steps, by the Icann Board,
would be a very welcome addition. <br>
<br>
best<br>
Mathieu<br>
<br>
<div class="moz-cite-prefix">Le 07/07/2015 21:46, Steve Crocker a
écrit :<br>
</div>
<blockquote cite="mid:037C8C13-C2AA-4A66-B9AF-C2FF2CA353B7@shinkuro.com" type="cite">
<pre wrap="">Avri,
Thanks for pointing to this. I took a quick look to see how easy it is to navigate.
I looked in particular at the Bylaws Drafting Process. Here’s the link and the PDF of the process is attached.
</pre>
<blockquote type="cite">
<pre wrap=""><a class="moz-txt-link-freetext" href="https://community.icann.org/download/attachments/50823981/Bylaw%20drafting%20process.pdf?version=1&modificationDate=1435910021000&api=v2">https://community.icann.org/download/attachments/50823981/Bylaw%20drafting%20process.pdf?version=1&modificationDate=1435910021000&api=v2</a>
</pre>
</blockquote>
<pre wrap="">The second page of the two page document is a very pretty and very readable diagram showing the six step process, with explicit attention to who is responsible, who contributes, who is informed, and who approves at each step. Five columns showing the role of the CCWG, SUBGROUP, ICANN LEGAL, INDEP. COUNSEL and BOARD are included.
As I’m sure you would expect, my attention focused immediately on the role the BOARD is expected to play during each of these six steps. The BOARD’s role is blank in steps 2-5. In steps 1 and 6 it is shown as “Informed.”
This leaves me puzzled. Under the existing bylaws and standard operating procedures, each bylaw change requires the board to take two actions, i.e. formal approval, not just being informed. The board first must pass a resolution approving the proposed language. When the proposed language is approved, the proposed bylaw change is posted for public comment. If the public comments are supportive, the board passes a second resolution formally adopting the change.
All parts of ICANN, including the board, have always treated bylaw changes as significant events. They are never done lightly or quickly. I fully appreciate the CCWG is also treating the proposed bylaw changes as significant, and the board stands ready to be supportive, but we must also observe the existing bylaws as we make these changes.
ICANN LEGAL is listed in the diagram as having a strong role throughout the process, and I can understand that from the outside it might seem that once ICANN LEGAL has spoken there’s nothing more for the BOARD to say, but I can assure you this is not how things work. The BOARD does indeed keep in close touch with ICANN LEGAL, but until the BOARD has formally passed resolutions adopting a bylaws change, the change cannot legally happen.
I recommend editing the document to include the formal requirements for adopting the resolutions. I am conscious in writing this that the title of the document is the Bylaw *drafting* process and that perhaps this is intended only as the front end of the entire process. If so, it means there will be steps beyond the six listed here to actually get the bylaws adopted. On the other hand, I suspect many will read this document as if it’s the complete process. Either way, it will help everyone to include the formal passage of resolutions in the overall picture.
Thanks,
Steve Crocker
writing on behalf of the ICANN board of directors
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">
On Jul 7, 2015, at 12:37 PM, Avri Doria <a class="moz-txt-link-rfc2396E" href="mailto:avri@acm.org"><avri@acm.org></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi
In the last few hours there has been a vast improvement.
<a class="moz-txt-link-freetext" href="https://community.icann.org/display/acctcrosscomm/Plenary+Drafts+for+CCWG-Accountability">https://community.icann.org/display/acctcrosscomm/Plenary+Drafts+for+CCWG-Accountability</a>
I actually went and found what I was looking for, instantly.
thank you
thank you
avri
---
This email has been checked for viruses by Avast antivirus software.
<a class="moz-txt-link-freetext" href="https://www.avast.com/antivirus">https://www.avast.com/antivirus</a>
_______________________________________________
Accountability-Cross-Community mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</pre>
</blockquote>
<pre wrap=""></pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Accountability-Cross-Community mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
*****************************
Mathieu WEILL
AFNIC - directeur général
Tél: +33 1 39 30 83 06
<a class="moz-txt-link-abbreviated" href="mailto:mathieu.weill@afnic.fr">mathieu.weill@afnic.fr</a>
Twitter : @mathieuweill
*****************************
</pre>
</div>
</blockquote></div><br></div></div></body></html>