<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; ">Hi Ed<div><br></div><div>Sorry I missed this one.</div><div><br><div><div>On Sep 9, 2013, at 3:07 AM, Edward Morris <<a href="mailto:edward.morris@ALUMNI.USC.EDU">edward.morris@ALUMNI.USC.EDU</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi,<div><br></div><div>Looking at the Board SIC proposal,</div></div></blockquote><div><br></div>You might want to provide a link or some explanation, I'm guessing not everyone here knows what you're referring to? I've not had time to look at it.</div><div><br><blockquote type="cite"><div dir="ltr"><div> now in it's response period, I noticed comments by the <span class="" style="">IPC</span> that actually make some sense. Namely:</div><div><br></div>
<div><br></div><div>1. Replacing the formal requirement to notify staff upon initiation of efforts to reform a Charter with a more informal suggestion that those managing the reform should consult with staff members early in the process.</div>
<div><br></div><div>I think that works better for us. I'm thinking particularly of those Bylaw reforms initiated by other than the EC. I'd hate to see such an effort thwarted because they didn't officially notify <span class="" style="">ICANN</span> early in the process. The fewer formal requirements Constituencies have in terms of notifying <span class="" style="">ICANN</span> the better. Informal processes should be preferred.</div></div></blockquote><div><br></div>I've already notified Rob and really don't have an issue consulting with him, think it's necessary. And a priori have no particular reason to back IPC (!), we have no idea what they're up to and why they think that matters.<br><blockquote type="cite"><div dir="ltr">
<div><br></div><div>2. The <span class="" style="">IPC</span> proposals in terms of the black hole between less than majority support and less than super majority opposition are commonsensical.</div></div></blockquote><div><br></div>Again, wa?<br><blockquote type="cite"><div dir="ltr"><div><br></div><div>3. Imposing a time limit on the Board to act to accept / reject Bylaws amendments is a good idea. Constituencies should not be at the indefinite mercy of the Board to enact changes to their own governing documents.</div></div></blockquote><br></div><div>So if the decisions are quicker constituencies are less at their mercy? </div><div><br></div><div>BTW, last time we went through this stuff time worked in our favor, we were able in Seoul to turn the SIC around on the NCSG charter after extended lobbying.</div><div><blockquote type="cite"><div dir="ltr">
<div><br></div><div><br></div><div>Do we have interest in endorsing the <span class="" style="">IPC</span> proposals during the Reply period? As we don't have a functioning PC I presume that responsibility falls to the EC. Might be a nice gesture to a Constituency we don't often agree with on matters of substance.</div></div></blockquote><div><br></div>Given the totality of our relationship, this is not the gesture that first comes to mind, but if the group feels differently I'm open to persuasion.</div><div><br></div><div>Thanks,</div><div><br></div><div>Bill<br><blockquote type="cite"><div dir="ltr">
<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Sep 7, 2013 at 4:37 PM, William Drake <span dir="ltr"><<a href="mailto:william.drake@uzh.ch" target="_blank">william.drake@uzh.ch</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi<div><br></div><div>Yesterday afternoon I had a long chat with Rob (the staffer responsible for us on operational matters) on a number of matters, e.g. bylaws revision, budget allocations, civil society roundtable, and proposed outreach and administrative funding. I'm rushing to deal with something else at the moment but will send a summary tomorrow. But before getting to that, I thought I should pass along the below. His bottom line is that there's no way our proposed timetable for revising the bylaws can work due to the turn around time need by the Board SIC committee, the public comment period, etc. So there's no point killing ourselves to complete a revision in October, since it can't go to NCUC members during the November election anyway. That said, there's also no reason not to begin dialogue and work on the issues with an eye to member adoption of a SIC-approved revision down the line somewhere, and in particular to address the most pressing outstanding item, which is whether to reboot the PC or establish some other formal process for the adoption of policy positions and statements.</div>
<div><br></div><div>More to come,</div><div><br></div><div>Bill<br><div><br><div>Begin forwarded message:</div><br><blockquote type="cite"><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span style="font-family: Helvetica; font-size: medium; "><b>From: </b></span><span style="font-family:'Helvetica';font-size:medium">Robert Hoggarth <<a href="mailto:robert.hoggarth@icann.org" target="_blank">robert.hoggarth@icann.org</a>><br>
</span></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span style="font-family: Helvetica; font-size: medium; "><b>Subject: </b></span><span style="font-family:'Helvetica';font-size:medium"><b>Re: NCUC Bylaws Revision</b><br>
</span></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span style="font-family: Helvetica; font-size: medium; "><b>Date: </b></span><span style="font-family:'Helvetica';font-size:medium">September 5, 2013 5:39:52 PM GMT+02:00<br>
</span></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span style="font-family: Helvetica; font-size: medium; "><b>To: </b></span><span style="font-family:'Helvetica';font-size:medium">William Drake <<a href="mailto:william.drake@uzh.ch" target="_blank">william.drake@uzh.ch</a>><br>
</span></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span style="font-family: Helvetica; font-size: medium; "><b>Cc: </b></span><span style="font-family:'Helvetica';font-size:medium">Glen de Saint Géry <<a href="mailto:Glen@icann.org" target="_blank">Glen@icann.org</a>><br>
</span></div><br><div style="word-wrap:break-word;font-size:14px;font-family:Calibri,sans-serif"><div>Hi Bill;</div><div><br></div><div>I think staff can certainly help the NCUC complete its internal efforts to amend its Charter by November, but I don't think you would have the second step --- Board approval -- completed by that time.</div>
<div><br></div><div>Even after a community elects to make charter amendments, those changes need to be "approved" by the ICANN Board. Even if you gave me formal notice today that the NCUC had voted to approve a charter change, I doubt that we would be able to get them approved by the Buenos Aires Board meeting. That is primarily because the current Board-approval process (at present less-than-formal, but soon to be formalized – see <a href="http://www.icann.org/en/news/public-comment/structures-charter-22jun13-en.htm" target="_blank">http://www.icann.org/en/news/public-comment/structures-charter-22jun13-en.htm</a>) includes the requirement for a Public Comment Forum for community review and comments on any proposed charter changes. So there is a minimum 21 – or 42 day -- period built into the process. </div>
<div><br></div><div>My observation is that these efforts always take longer than expected. It wouldn't be a bad idea to get a group started asap even if its just to discuss and outline potential changes and staff (me and our experienced consultant Ken Bour) would be delighted to support the effort. Staff is not an "approval" bottle neck in any effort, but in my experience the Board is more comfortable with charter changes when they know that community leaders and staff have been engaged in an active dialogue. We can also highlight potential problem areas and suggest solutions so that any Board concerns can be anticipated and resolved before the changes/amendments are announced. </div>
<div><br></div><div>I am happy to chat about this with anyone from the NCUC you designate on this. Please feel free to share this note with any of those folks who are itching to get started. Let's discuss on our call tomorrow.</div>
<div><br></div><div>Best,</div><div><br></div><div>Rob</div></div></blockquote></div><br></div></div><br>_______________________________________________<br>
Ncuc-ec mailing list<br>
<a href="mailto:Ncuc-ec@lists.ncuc.org">Ncuc-ec@lists.ncuc.org</a><br>
<a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec" target="_blank">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br><div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); font-family: Palatino; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="color: rgb(0, 0, 0); font-family: Palatino; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="color: rgb(0, 0, 0); font-family: Palatino; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">**********************************************************<br>William J. Drake<br>International Fellow & Lecturer<br> Media Change & Innovation Division, IPMZ<br> University of Zurich, Switzerland<br>Chair, Noncommercial Users Constituency, <br> ICANN, <a href="http://www.ncuc.org">www.ncuc.org</a><br><a href="mailto:william.drake@uzh.ch">william.drake@uzh.ch</a> (w), <a href="mailto:wjdrake@gmail.com">wjdrake@gmail.com</a> (h),<br> <a href="http://www.williamdrake.org">www.williamdrake.org</a><br>***********************************************************</div></div></div>
</div>
<br></div></body></html>