<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Calibri;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:Calibri;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Councilors –<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">As discussed in Hyderabad, the SO/ACs are pushing ICANN Staff to get an early start on planning for ICANN58, in an effort to avoid/mitigate some of the pain points experienced at ICANN57.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">To this end, Staff has prepared the attached document (PDF), outlining the timeline for finalizing the ICANN58 schedule, along with two draft “Block Schedules”: one with a single Constituency Day, the other
with a split Constituency Day(s). Finally, the PDF displays results and feedback gathered from the meeting survey.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">SO/AC leaders (including Donna, Heather and myself) are planning to meet with ICANN Meeting Staff in early December to discuss the Block Schedule. Questions for the GNSO Council:<br>
<br>
(1) Do we prefer a Single or Split Constituency Day?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">(2) What is the right number of High Interest Topics (HIT)? The current Block Schedule drafts contain five HIT sessions.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">(3) Any thoughts on the best way to solicit topics for HIT sessions, and how to choose the top 5?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">(4) Similarly, any thoughts on how to address the inevitable conflicts between working sessions and HITs?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">(5) Any other specific feedback you’d like us to bring to the SO/AC meeting<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;color:black">Please respond by next week with your ideas, and we’ll take them back to the planning group.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Thanks—<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">J.</span><o:p></o:p></p>
</div>
</body>
</html>