<div dir="ltr"><div class="gmail_extra">hi all,</div><div class="gmail_extra"><br></div><div class="gmail_extra">this a reminder to get the votes/endorsement for the statement.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Best,</div><div class="gmail_extra"><br></div><div class="gmail_extra">Rafik<br>
<br><div class="gmail_quote">2017-05-09 22:57 GMT+09:00 Rafik Dammak <span dir="ltr"><<a href="mailto:rafik.dammak@gmail.com" target="_blank">rafik.dammak@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra">Hi Matt,</div><div class="gmail_extra"><br></div><div class="gmail_extra">thanks for the amendments,</div><div class="gmail_extra">we need to endorse the comment within 24 hours. please, all PC members share your thoughts and if you endorsing or not the statement.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Best,</div><div class="gmail_extra"><br></div><div class="gmail_extra">Rafik</div><div><div class="h5"><div class="gmail_extra">
<br><div class="gmail_quote">2017-05-09 18:36 GMT+09:00 Matthew Shears <span dir="ltr"><<a href="mailto:matthew@intpolicy.com" target="_blank">matthew@intpolicy.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi<br>
<br>
Would be good if I included the right link:<br>
<br>
<a href="https://docs.google.com/document/d/1KPaILgBF3EhSGM2NmcyUlscuF77wDFxlgyOIebl1ZYo/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/docume<wbr>nt/d/1KPaILgBF3EhSGM2NmcyUlscu<wbr>F77wDFxlgyOIebl1ZYo/edit?usp=s<wbr>haring</a><br>
<br>
Thanks to Ayden for noticing.<br>
<br>
Matthew<br>
<br>
<br>
On 09/05/2017 09:39, Matthew Shears wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all<br>
<br>
Based on the feedback I have substantially redrafted and shortened our submission.<br>
<br>
Please edit in the doc.<br>
<br>
<a href="https://docs.google.com/a/thefactory21.com/document/d/1KPaILgBF3EhSGM2NmcyUlscuF77wDFxlgyOIebl1ZYo/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/a/thef<wbr>actory21.com/document/d/1KPaIL<wbr>gBF3EhSGM2NmcyUlscuF77wDFxlgyO<wbr>Iebl1ZYo/edit?usp=sharing</a> <br>
<br>
Deadline tomorrow Wed 10 23.59 UTC.<br>
<br>
Matthew<br>
<br>
<br>
On 08/05/2017 18:13, avri doria wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
observer view: sounds good<br>
<br>
not sure the last bullet is needed. the fact that we are doing this<br>
through the proper process is good as a test but is that a reason for<br>
doing it? but it seems ok to include it.<br>
<br>
avri<br>
<br>
<br>
<br>
On 08-May-17 10:25, Matthew Shears wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks all for the comments.<br>
<br>
Given the discussion, I am wondering whether or not we need to make a<br>
submission on this (there is only one so far - from AFNIC).<br>
<br>
If we feel we do, we could in a short statement:<br>
<br>
* Endorse the proposal for the creation of the Board Accountability<br>
Mechanisms Committee (BAMC)<br>
* Recognize the importance of and the need to respect the process<br>
for changing the fundamental bylaws<br>
* State that the proposed change is a useful and non-controversial<br>
way to engage and trial the associated accountability mechanisms<br>
<br>
What other points could be added?<br>
<br>
Thanks.<br>
<br>
Matthew<br>
<br>
<br>
<br>
<br>
On 07/05/2017 07:58, David Cake wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We need to fully respect the process for changing the fundamental bylaws. I have absolutely no problem with the proposed change to do so - and actually, I think an uncontroversial change like this is a good trial for those processes.<br>
<br>
I agree with Milton that while change is uncontroversial, it not only is it a fundamental bylaw, it is part of the accountability mechanisms, and we should insist that accountability mechanisms are changed only with due community process.<br>
<br>
While I think in general we should avoid micromanaging board internal processes to this extent, and I understand the reasoning behind taking mention of a specific board committee out of bylaws, in practice the current wording is a very simple and easy to understand change, and wording that removed mention of a specific committee would be more complex and potentially more ambiguous. If a committee was created specifically for dealing with Accountability processes, it's unlikely any future changes would be necessary (the board could effectively recombine committees in the future if it wished without a bylaws change IMO).<br>
<br>
David<br>
<br>
Sent from my iPad<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 6 May 2017, at 5:42 am, avri doria <<a href="mailto:avri@APC.ORG" target="_blank">avri@APC.ORG</a>> wrote:<br>
<br>
hi,<br>
<br>
Perhaps the problem is that we need to change the fundamental bylaws to<br>
take deciding on board committees out of the fundamental bylaws.<br>
<br>
but in any case, got to do something about the bylaws.<br>
<br>
avri<br>
<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 05-May-17 15:23, Mueller, Milton L wrote:<br>
<br>
Hi, Matt<br>
<br>
There is not, and should not be, any way around this. The problem is<br>
not that ICANN needs a fundamental bylaw change to “create a new<br>
committee,” it is that Article 4 sec 3 of the bylaws, which is<br>
designated as “fundamental,” specifically names the BGC as the handler<br>
of Reconsideration requests. (““The Board has designated the Board<br>
Governance Committee to review and consider any such Reconsideration<br>
Requests.”)<br>
<br>
<br>
<br>
Article 4 is also the home of a lot of other “Accountability and<br>
Review” stuff that we definitely do not want the board messing with<br>
without community approval.<br>
<br>
<br>
<br>
So the board needs approval for this and should have to do through<br>
this exercise. But if the board decides to create a new “Committee to<br>
organize birthday celebrations” or a “Committee to Honor Snapping<br>
Turtles” I don’t think there would be any problem.<br>
<br>
And going forward, I guess ICANN legal and the rest of us will be<br>
mindful of future flexibility when deciding where to put things in the<br>
bylaws.<br>
<br>
<br>
<br>
Dr. Milton L Mueller<br>
<br>
Professor, School of Public Policy <<a href="http://spp.gatech.edu/" rel="noreferrer" target="_blank">http://spp.gatech.edu/</a>><br>
<br>
Georgia Institute of Technology<br>
<br>
Internet Governance Project<br>
<br>
<a href="http://internetgovernance.org/" rel="noreferrer" target="_blank">http://internetgovernance.org/</a><br>
<br>
<br>
<br>
<br>
<br>
One issue that has been raised is that it seems silly to have to have<br>
a fundamental bylaw change for the Board to be able to create a new<br>
committee. It is not clear that there is anyway around this but would<br>
love to hear otherwise.<br>
<br>
Looking forward to your comments.<br>
<br>
</blockquote>
---<br>
This email has been checked for viruses by Avast antivirus software.<br>
<a href="https://www.avast.com/antivirus" rel="noreferrer" target="_blank">https://www.avast.com/antiviru<wbr>s</a><br>
</blockquote>
---<br>
This email has been checked for viruses by AVG.<br>
<a href="http://www.avg.com" rel="noreferrer" target="_blank">http://www.avg.com</a><br>
<br>
</blockquote>
-- <br>
Matthew Shears<br>
<a href="mailto:matthew@intpolicy.com" target="_blank">matthew@intpolicy.com</a><br>
<a href="tel:%2B447712472987" value="+447712472987" target="_blank">+447712472987</a><br>
Skype:mshears<br>
<br>
<br>
______________________________<wbr>_________________<br>
NCSG-PC mailing list<br>
<a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/<wbr>listinfo/ncsg-pc</a><br>
</blockquote>
______________________________<wbr>_________________<br>
NCSG-PC mailing list<br>
<a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/<wbr>listinfo/ncsg-pc</a><br>
</blockquote>
<br><span class="m_-142905747799300392HOEnZb"><font color="#888888">
</font></span></blockquote><span class="m_-142905747799300392HOEnZb"><font color="#888888">
<br>
-- <br>
Matthew Shears<br>
<a href="mailto:matthew@intpolicy.com" target="_blank">matthew@intpolicy.com</a><br>
<a href="tel:%2B447712472987" value="+447712472987" target="_blank">+447712472987</a><br>
Skype:mshears<br>
<br>
______________________________<wbr>_________________<br>
NCSG-PC mailing list<br>
<a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/<wbr>listinfo/ncsg-pc</a><br>
</font></span></blockquote></div><br></div></div></div></div>
</blockquote></div><br></div></div>