<html><head><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="">Hi<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 20, 2015, at 8:22 AM, Arun Mohan Sukumar <<a href="mailto:arunmohan.s@gmail.com" class="">arunmohan.s@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Bill, good points - you're right about the need to re-vision this into a holistic exercise. What can we do going ahead to ensure that there is momentum in completing this exercise, even if it is not bound to a strict timeline? As for the text, the letters in black seem identical to the actual charter, but I suppose the added text, even if in a different colour, may appear confusing to folks.<div class=""><br class=""></div><div class="">One way to go ahead with this is to open the call at the end of this month to all willing NCUC members and make it into a brainstorming exercise. Before we begin, i can present a list of barebones changes we ought to make for NCSG conformity --- and the discussion can go forward on larger review questions.</div></div></div></blockquote><div><br class=""></div>Sounds good to me. I’d think it would make sense before we do a call if others could get some of their top-level suggestions on the table as well.</div><div><br class=""></div><div>As a starting point, what about having team members reply with points under the following sorts of headings:</div><div><br class=""></div><div>1. Overarching Issues (holistic view of what’s needed)</div><div><br class=""></div><div>2. NCSG Charter Conformity Issues</div><div><br class=""></div><div>3. Discrepancies with Current Practices to Close</div><div><br class=""></div><div>4. “Would be Nice” Improvements</div><div><br class=""></div><div>or some similar parsing…let’s agree the categories and then start tossing our points in.</div><div><br class=""></div><div>Re: the meeting, I’m looking at <a href="http://doodle.com/ncngb2w5tecmn3as" class="">http://doodle.com/ncngb2w5tecmn3as</a> and it seems like the two end of the month options are not working so well for people, there’s an awful lot of pink boxes. Time zone appears to be a challenge for Rafik, who’d I’d think should be on the call(s). 17:30-19:00 seems a winner for everyone but him because it’s the middle of the night in Japan. Could people maybe take a second look at their schedules and see if they could make one of the 15:30-17:00 slots work?</div><div><br class=""></div><div>We also need replies from more people…I count 27 people in this team and just 6 Doodle replies. We can’t revise they bylaws with that level of participation…</div><div><br class=""></div><div>Best</div><div><br class=""></div><div>Bill </div><div><br class=""></div><div><br class=""></div><div><br class=""></div><br class=""><br class=""><div apple-content-edited="true" class="">
<div style="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; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">*********************************************************<br class="">William J. Drake<br class="">International Fellow & Lecturer<br class=""> Media Change & Innovation Division, IPMZ<br class=""> University of Zurich, Switzerland<br class="">Chair, Noncommercial Users Constituency, <br class=""> ICANN, <a href="http://www.ncuc.org" class="">www.ncuc.org</a><br class=""><a href="mailto:william.drake@uzh.ch" class="">william.drake@uzh.ch</a> (direct), <a href="mailto:wjdrake@gmail.com" class="">wjdrake@gmail.com</a> (lists),<br class=""> <a href="http://www.williamdrake.org" class="">www.williamdrake.org</a><br class=""><i class="">Internet Governance: The NETmundial Roadmap </i><a href="http://goo.gl/sRR01q" class="">http://goo.gl/sRR01q</a><br class="">*********************************************************</div>
</div>
<br class=""></div></body></html>