<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" id="owaParaStyle" style="display: none; ">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body dir="ltr" fpstyle="1" aria-label="Corpo del messaggio" tabindex="0" style="">
<div name="divtagdefaultwrapper" id="divtagdefaultwrapper" style="font-family: Calibri,Arial,Helvetica,sans-serif; font-size: 12pt; color: #000000; margin: 0">
<p>Small correction: I would like to attend at least part of the ISA conference in Toronto. It starts on the 26th. Maybe I should leave Singapore (if I end up coming, that is) on the 27 or 28th.</p>
<div>
<p><br>
</p>
<p><br>
</p>
<div name="divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<div>
<div>
<div>
<div class="BodyFragment"><font size="2"><font face="Helvetica, sans-serif"></font>
<div class="PlainText"><br>
</div>
</font></div>
</div>
</div>
</div>
</div>
</div>
<div style="color: rgb(40, 40, 40); ">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Da:</b> ncuc-ec-bounces@lists.ncuc.org <ncuc-ec-bounces@lists.ncuc.org> per conto di William Drake <wjdrake@gmail.com><br>
<b>Inviato:</b> lunedì 23 dicembre 2013 16.47<br>
<b>A:</b> NCUC EC<br>
<b>Oggetto:</b> [NCUC-EC] Who Can Come to Singapore?</font>
<div> </div>
</div>
<div>Hello
<div><br>
</div>
<div>I know it’s the holiday season but I really need to hear back from people on the following. As I’ve mentioned a number of times on the ncuc-discuss list and at Constituency Day and related meetings, last year I applied for and received budget support
to do two special events in Singapore just prior to the meeting: 1) $6,950 for a new NCUC EC ‘retreat’ of sorts on Thursday 20 March to discuss working methods, set plans, and get people up to speed a bit on ICANN and GNSO; and 2) and $11,100 for a policy
conference on 21 March. After an extended bit of bugging staff I’ve finally just received confirmation that we do have a conference space on the 21st for 150 people, so that’s on, and we’ll need soon to start getting the word out. </div>
<div><br>
</div>
<div>The next things I'll need to do are discuss with Fadi and senior staff 1) possible budgetary adjustments for travel, 2) logistics for the two events, and 3) finances regarding the conference—I’ve had prior conversations about focusing the meeting on IG
@ Brazil and beyond (perhaps including the High Level Panel, which is no longer calling itself that, but I can’t get into the new acronym for the Panel on the Future of Internet Governance Cooperation and Mechanisms) and making it more open to the wider community
in exchange for increased financial support, and need to follow up with a concrete proposal.</div>
<div><br>
</div>
<div>Against that backdrop, this message concerns item 1. </div>
<div><br>
</div>
<div>Since last year, ICANN provides NCUC with three fully funded travel slots per meeting (economy flight, conference hotel, per diem). One goes to the chair, who has to be there to run Constituency Day and do other stuff. The other two have gone to EC members---
although in principle if there was a member involved in other stuff, such as a ‘hot’ policy process that would be debated at a given meeting the EC could decide to fund such a person instead. That didn’t happen last year, but we did dip into NCUC’s a bit
for some support (I’ll send a separate message about financial/budgetary stuff). In addition, NCSG receives slots 3 per meeting, one of which would go to a NCUC rep on the NCSG EC (could be the NCSG PC as well, I suppose). </div>
<div><br>
</div>
<div>Bottom line: for the retreat, at present we have a special budget allocation that would cover the logistics (room, comms, transcription, etc.) and the extra night of hotel; and regular travel support for at least two of the five regional EC members to
come to Singapore. An additional extra night of hotel is also possibly coverable through conference support, or we could do something through NCUC existing funds or some new fundraising, TBD.</div>
<div><br>
</div>
<div>The immediate question is what to do about the other three EC members flights and hotels for the week. One option we’ve pursued in the past is to split up the travel allotments, e.g. someone takes the plane and another takes the hotel and then we try
to find cheap alternatives for the missing parts with NCUC funds, but ICANN Accounting Dept. doesn’t like doing this. What I will do instead is try to bug them into doing something else they don’t like to do, which is reallocate funds they’ve awarded us in
principle. Maybe we could meet informally outside the conference venue without the comms and other logistics in order to save on the thousands ICANN would spend on that. Or maybe they could reallocate the monies promised for print materials that we haven’t
used. Or we can dip into NCUC’s bank account, although preferably not further than $5000….we’ll see what makes sense. Worst comes to worst, we might have to have someone participating remotely—ICANN’s RM is generally very good, but this is of course not
the preferred approach. </div>
<div><br>
</div>
<div>But before I get into any of this with staff, I need to know who is able to come to Singapore. There’s no point in haggling and harassing them to change budget allocations etc. if some folks are unable to attend anyway. So I need to hear from all five
of you: If there is travel support, can you come to Singapore</div>
<div><br>
</div>
<div>a) For the retreat, which would mean the arriving the 19th </div>
<div><br>
</div>
<div>b) For the policy conference, which if you’re not already there would mean arriving the 20th </div>
<div><br>
</div>
<div>c) For the ICANN meeting itself, the normal travel support being Friday 21st check and Friday 28th check out.</div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>Bill</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
<div>
<div style="color:rgb(0,0,0); font-family:Palatino; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:2; text-indent:0px; text-transform:none; white-space:normal; widows:2; word-spacing:0px; word-wrap:break-word">
<div style="color:rgb(0,0,0); font-family:Palatino; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:2; text-indent:0px; text-transform:none; white-space:normal; widows:2; word-spacing:0px; word-wrap:break-word">
<div style="color:rgb(0,0,0); font-family:Palatino; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:2; text-indent:0px; text-transform:none; white-space:normal; widows:2; word-spacing:0px; word-wrap:break-word">
<div style="color:rgb(0,0,0); font-family:Palatino; font-style:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:2; text-indent:0px; text-transform:none; white-space:normal; widows:2; word-spacing:0px; word-wrap:break-word">
**********************************************************<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>
</div>
<br>
</div>
</div>
</div>
</div>
<meta name="ProgId" content="Word.Document">
<meta name="Generator" content="Microsoft Word 14">
<meta name="Originator" content="Microsoft Word 14">
<link rel="File-List" href="eui%20footer_files/filelist.xml"><link rel="themeData" href="eui%20footer_files/themedata.thmx"><link rel="colorSchemeMapping" href="eui%20footer_files/colorschememapping.xml"><style> <!-- /* Font Definitions */ @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-520092929 1073786111 9 0 415 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line-height:115%;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.WordSection1 {page:WordSection1;} --> </style><style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso-para-margin-right:0in; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} </style>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:8.0pt;color:#595959"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;color:#595959">The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination,
distribution, forwarding, or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited without the express permission of the sender. If you received this communication in
error, please contact the sender and delete the material from any computer. <o:p>
</o:p></span></p>
</div>
</body>
</html>