<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none"><!-- p { margin-top: 0px; margin-bottom: 0px; }--></style>
</head>
<body dir="ltr">
<div id="OWAFontStyleDivID" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p style="">Hi Bill, everyone: I trust you Bill on this. I ok with option 1, too. <br>
</p>
<div>
<p style=""><br>
</p>
</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> sabato 3 maggio 2014 10.06<br>
<b>A:</b> Exec. Comm<br>
<b>Oggetto:</b> [NCUC-EC] ICANN 50 possible Thursday change</font>
<div> </div>
</div>
<div>Hi
<div><br>
</div>
<div>I’m guessing this might not be of intense local interest but just in case, Steve proposed a schedule change, I and several other SO AC leaders grumped, he’s come back with options. I’m inclined toward solution 1 on a one-time only basis to avoid any precedent
that the public forum be reduced, as are some others. Newest at top.
<div><br>
</div>
<div>Any thoughts, please share ASAP.</div>
<div><br>
</div>
<div>Thanks</div>
<div><br>
</div>
<div>Bill</div>
<div><br>
</div>
<div><br>
<div>
<div>Begin forwarded message:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="margin-top:0px; margin-right:0px; margin-bottom:0px; margin-left:0px">
<span style="font-family:'Helvetica'"><b>From: </b></span><span style="font-family:'Helvetica'">Steve Crocker <<a href="mailto:steve@shinkuro.com">steve@shinkuro.com</a>><br>
</span></div>
<div style="margin-top:0px; margin-right:0px; margin-bottom:0px; margin-left:0px">
<span style="font-family:'Helvetica'"><b>Subject: </b></span><span style="font-family:'Helvetica'"><b>Re: [Soac-infoalert] ICANN 50 possible Thursday change</b><br>
</span></div>
<div style="margin-top:0px; margin-right:0px; margin-bottom:0px; margin-left:0px">
<span style="font-family:'Helvetica'"><b>Date: </b></span><span style="font-family:'Helvetica'">May 2, 2014 at 9:01:35 PM GMT+2<br>
</span></div>
<div style="margin-top:0px; margin-right:0px; margin-bottom:0px; margin-left:0px">
<span style="font-family:'Helvetica'"><b>To: </b></span><span style="font-family:'Helvetica'"><a href="mailto:soac-infoalert@icann.org">soac-infoalert@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'"><b>Cc: </b></span><span style="font-family:'Helvetica'">Sally Costerton <<a href="mailto:sally.costerton@icann.org">sally.costerton@icann.org</a>>, "Tanzanica S. King" <<a href="mailto:tanzanica.king@icann.org">tanzanica.king@icann.org</a>>,
Jim Trengrove <<a href="mailto:jim.trengrove@icann.org">jim.trengrove@icann.org</a>>, Icann-board ICANN <<a href="mailto:icann-board@icann.org">icann-board@icann.org</a>>, Nick Tomasso <<a href="mailto:nick.tomasso@icann.org">nick.tomasso@icann.org</a>>, Theresa
Swinehart <<a href="mailto:theresa.swinehart@icann.org">theresa.swinehart@icann.org</a>>, Duncan Burns <<a href="mailto:duncan.burns@icann.org">duncan.burns@icann.org</a>><br>
</span></div>
<br>
<div>
<div style="word-wrap:break-word"><span style="font-family:Cambria; font-size:large">Folks,</span><br>
<div><font face="Cambria" size="4"><br>
</font></div>
<div><font face="Cambria" size="4">Sally Costerton and I t<span style="">hank you all for your helpful responses to my earlier note on the idea of changing the Thursday agenda to accommodate more time for the public dialogue we need to deliver at our forthcoming
London meeting. We are acutely conscious that the combination several major one-off events - the High Level Government Meeting (HLGM) and the two public consultations are putting significant pressure on the agenda for ICANN50. </span></font></div>
<div>
<div dir="auto">
<div><span style=""><font face="Cambria" size="4"><br>
</font></span></div>
<div><span style=""><font face="Cambria" size="4">We are juggling trying to maximise flexibility for SOACs to do their work, access to the HLGM and the need to provide slots for Hot Topics for cross community dialogue with minimal agenda conflict. </font></span></div>
<div><span style=""><font face="Cambria" size="4"><br>
</font></span></div>
<div><font face="Cambria" size="4">Having considered your feedback and consulted with staff, we suggest two options below.
<u><b>Please pick one and let us know over the next day or two.</b></u></font></div>
<div><span style=""><font face="Cambria" size="4"><br>
</font></span></div>
<div>
<ol>
<li><span style=""><font face="Cambria" size="4">We make the changes to Thursday as suggested and support this by running an additional IANA stewardship transition session on Monday after the opening session and provide support to the SOAC groups to find alternative
slots on the agenda in addition to the early Thursday slot as needed. We pilot remote hubs using two-way video and hopefully a YouTube channel. The use of remote hubs actually doubled participation at NETmundial so could be a real opportunity to diversify
input.<br>
<br>
<br>
</font></span></li><li><span style=""><font face="Cambria" size="4">We keep Thursday as it usually runs with a four hour public forum and run two
<span style="">consultation sessions - one on the IANA stewardship transition and one on the ICANN accountability dialogue on a 'normal' schedule - this would be Monday or Wednesday to get time that is minimally conflicted. This would be much like Singapore.
We would not set up the video remote hubs in this case or possibly the YouTube channel. This would maintain the full Public Forum but reduce the time and attention for the two consultation sessions. Also the Monday sessions will have to run parallel to
the HLGM and we know that UKG have requested a session on IANA oversight transition led by Larry Strickling. </span></font></span></li></ol>
</div>
<div><span style=""><font face="Cambria" size="4"><br>
</font></span></div>
<div><span style=""><font face="Cambria" size="4">Finally we are very aware that the community wants to improve the issue of agenda conflict at ICANN meetings. This topic was addressed in detail by the Meeting Strategy Working Group which recently had its
report out for public comment. There was a previous opportunity to see this but in case you haven’t, not here is a copy of the recommendations
<a href="http://www.icann.org/en/groups/board/participation/mswg/recommendations-25feb14-en.pdf">
http://www.icann.org/en/groups/board/participation/mswg/recommendations-25feb14-en.pdf</a></font></span></div>
<div><font face="Cambria" size="4"><br>
</font></div>
<div><span style=""><font face="Cambria" size="4">If you can let us know which option you prefer over the next 48 hours we would appreciate it. If we go for option 1 we need to let the community know early next week so that they can confirm travel and we can
start the call to set up the hubs.</font></span></div>
<div><span style=""><font face="Cambria" size="4"><br>
</font></span></div>
<div><span style=""><font face="Cambria" size="4">Thanks,</font></span></div>
<div><span style=""><font face="Cambria" size="4"><br>
</font></span></div>
<div><span style=""><font face="Cambria" size="4">Steve Crocker and Sally Costerton</font></span></div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</div>
<div><br>
</div>
<div>
<div style="margin:0px"><span style="font-family:Helvetica"><b>From: </b></span><span style="font-family:Helvetica">William Drake <<a href="mailto:wjdrake@gmail.com">wjdrake@gmail.com</a>><br>
</span></div>
<div style="margin:0px"><span style="font-family:Helvetica"><b>Subject: </b></span><span style="font-family:Helvetica"><b>Re: [Soac-infoalert] ICANN 50 possible Thursday change</b><br>
</span></div>
<div style="margin:0px"><span style="font-family:Helvetica"><b>Date: </b></span><span style="font-family:Helvetica">April 27, 2014 at 2:29:48 PM GMT+2<br>
</span></div>
<div style="margin:0px"><span style="font-family:Helvetica"><b>To: </b></span><span style="font-family:Helvetica">Steve Crocker <<a href="mailto:steve@shinkuro.com">steve@shinkuro.com</a>><br>
</span></div>
<div style="margin:0px"><span style="font-family:Helvetica"><b>Cc: </b></span><span style="font-family:Helvetica">"<a href="mailto:SOAC-infoalert@icann.org">SOAC-infoalert@icann.org</a>" <<a href="mailto:SOAC-infoalert@icann.org">SOAC-infoalert@icann.org</a>><br>
</span></div>
<br>
<div>Hi Steve<br>
<br>
NCUC folks think the Public Forum is pretty important and have never been wild about suggestions to shorten it. On the other hand, since we lost Fridays we’ve gotten used to schedule implosions and forced choices between equally essential sessions that reduce
our ability to participate effectively in ICANN. So if Thursday’s really the only option for the accountability and IANA discussions that obviously need to happen, ok let’s do that.<br>
<br>
Cheers,<br>
<br>
Bill<br>
<br>
On Apr 25, 2014, at 5:42 PM, Steve Crocker <<a href="mailto:steve@shinkuro.com">steve@shinkuro.com</a>> wrote:<br>
<br>
<blockquote type="cite">SO and AC chairs,<br>
<br>
As you know, ICANN50 is fast approaching and post NETmundial we are now turning our thoughts to the tricky subject of how to ensure that we carve out enough quality time in the agenda to handle effective and comprehensive public dialogues on the Transition
of the NTIA Stewardship of the IANA function as well as the new ICANN Accountability track. These will both require a chunk of non-conflicted time in London and the ability to offer high quality remote access to maximise participants from around the world.
<br>
<br>
To the latter, we're exploring the possibility of setting up a series of remote hubs as some of you will have seen used at NETmundial to great acclaim. We will explore this idea further over the next week or so and keep you updated.<br>
<br>
On the scheduling point, we'd like to suggest that for this meeting only we reshuffle the planned Thursday agenda. Currently our thinking is that we start the morning at 8.30 to allow those groups having wrap up sessions to handle those requirements between
8.30 and 10am. We follow this with a two hour session on ICANN Accountability followed by an early lunch break and then run a session on the Transition of the NTIA Stewardship of the IANA function from 1-3 or 3.30. This is the most effective time slot to
maximise international participation. We'd run a shorter Public Forum from 4 - 6 and wrap up with a public Board meeting finishing at 7 and then Cocktails.<br>
<br>
The RSSAC would like an open session during the meeting and we'd propose to put that into a Monday afternoon slot. We anticipate that two hours will probably be adequate for the Public Forum because the Transition of the NTIA Stewardship of the IANA function
and ICANN Accountability topics will be very important for the community and would likely take up a chunk of the public forum under normal cirumstances. <br>
<br>
If you are in agreement with this suggestion we'd like to communicate it this week to enable people to firm up their travel plans. <br>
<br>
Please let us know your thoughts in the next day or two.<br>
<br>
Thank you.<br>
<br>
Steve.<br>
<br>
</blockquote>
</div>
</div>
<br>
</div>
</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>