<html xmlns:v="urn:schemas-microsoft-com:vml" 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:mv="http://macVmlSchemaUri" 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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Calibri;}
span.EmailStyle18
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal-reply;
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-size:10.0pt;}
@page WordSection1
{size:595.0pt 842.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1451363472;
mso-list-type:hybrid;
mso-list-template-ids:1583255490 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Thanks Wolf-Ulrich. Updated summary is attached.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black">WUKnoben <wolf-ulrich.knoben@t-online.de><br>
<b>Reply-To: </b>WUKnoben <wolf-ulrich.knoben@t-online.de><br>
<b>Date: </b>Thursday 1 December 2016 at 16:46<br>
<b>To: </b>Emily Barabas <emily.barabas@icann.org>, Phil Corwin <psc@vlaw-dc.com>, GNSO Council List <council@gnso.icann.org><br>
<b>Subject: </b>Re: [council] Re: [EXTERNAL] RE: Consolidated input on ICANN58 planning<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman""><o:p> </o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:black">Thanks Emily,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">here’s some ISPCP constituency input:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">1) Do we prefer a Single or Split Constituency Day?
</span><span style="font-size:11.0pt;color:red">Single day</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">(2) What is the right number of High Interest Topics (HIT)? The current Block Schedule drafts contain five HIT sessions.
</span><span style="font-size:11.0pt;color:red">Max of 4, preference is 3 per meeting. ICANN meetings should be focused on core activities whether an A, B or C meeting, not HITs.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">(3) Any thoughts on the best way to solicit topics for HIT sessions, and how to choose the top 5? (</span><span style="font-size:11.0pt;color:red">Best of 4 max) Seek topics via SOAC list, list
topics supported, allow all SO/AC/Cs to select preferences in order.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">(4) Similarly, any thoughts on how to address the inevitable conflicts between working sessions and HITs?
</span><span style="font-size:11.0pt;color:red">Reducing the number of HITs reduces conflicts. Limiting HITs to 3 greatly reduces this problem. Working sessions should be the priority.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">(5) Any other specific feedback you’d like us to bring to the SO/AC meeting.
</span><span style="font-size:11.0pt;color:red">Hard code parts of the program <u>
BEFORE</u> defining block schedules e.g. GNSO Council, GNSO meetings with Board, GAC, and CCSO, ASO mtg, CSG open meeting, parts of the CCSO meetings, Open Forum (prefer all on one day), Board Meeting etc,</span><span style="color:black"><o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:black"><br>
Best regards<br>
<br>
Wolf-Ulrich<o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Tahoma;color:black"> <o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:Tahoma;color:black">From:</span></b><span style="font-size:10.0pt;font-family:Tahoma;color:black"> Emily Barabas
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:Tahoma;color:black">Sent:</span></b><span style="font-size:10.0pt;font-family:Tahoma;color:black"> Thursday, December 1, 2016 9:10 AM<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:Tahoma;color:black">To:</span></b><span style="font-size:10.0pt;font-family:Tahoma;color:black"> Phil Corwin ; GNSO Council List
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:whitesmoke"><b><span style="font-size:10.0pt;font-family:Tahoma;color:black">Subject:</span></b><span style="font-size:10.0pt;font-family:Tahoma;color:black"> [council] Re: [EXTERNAL] RE: Consolidated input on ICANN58
planning<o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">I have updated the summary document (attached) to include comments from the BC.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Kind regards,</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Emily</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black">Phil Corwin <psc@vlaw-dc.com><br>
<b>Date: </b>Wednesday 30 November 2016 at 18:36<br>
<b>To: </b>Emily Barabas <emily.barabas@icann.org>, GNSO Council List <council@gnso.icann.org><br>
<b>Subject: </b>[EXTERNAL] RE: Consolidated input on ICANN58 planning<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Weighing in for the BC:</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="color:black"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;color:#1F497D">Prefer single Constituency Day</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="color:black"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;color:#1F497D">One HIT that the community has broad agreement on, and no more than 3 maximum for entire meeting.
</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="color:black"><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;color:#1F497D">Staff should create a process for requests for HIT’s that makes it fair and equitable for all who have requested topics and that looks toward achieving SO/AC consensus; and ICANN staff
should moderate any HIT and should select panelists to ensure opportunity for each SOAC to be represented.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="color:black"><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;color:#1F497D">Conflicts will be substantially minimized via early review of draft schedule and limiting HIT sessions to no more than 1-3.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">We did not discuss whether the A meeting should look more like the B or C.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Hope that is useful.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Best regards, Philip</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:Tahoma;color:navy">Philip S. Corwin, Founding Principal</span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:Tahoma;color:navy">Virtualaw LLC</span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:Tahoma;color:navy">1155 F Street, NW</span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:Tahoma;color:navy">Suite 1050</span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:Tahoma;color:navy">Washington, DC 20004</span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:Tahoma;color:navy">202-559-8597/Direct</span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:Tahoma;color:navy">202-559-8750/Fax</span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:Tahoma;color:navy">202-255-6172/Cell</span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:Tahoma;color:navy"> </span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:Tahoma;color:navy">Twitter: @VlawDC</span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Tahoma;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size:10.0pt;font-family:Tahoma;color:navy">"Luck is the residue of design" -- Branch Rickey</span></i></b><span style="color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:Tahoma;color:black">From:</span></b><span style="font-size:10.0pt;font-family:Tahoma;color:black"> owner-council@gnso.icann.org [mailto:owner-council@gnso.icann.org]
<b>On Behalf Of </b>Emily Barabas<br>
<b>Sent:</b> Wednesday, November 30, 2016 3:54 AM<br>
<b>To:</b> GNSO Council List<br>
<b>Subject:</b> [council] Consolidated input on ICANN58 planning</span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Dear Councilors,</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Item 11 on the agenda of the December 1 Council meeting is a discussion on planning for ICANN58. On November 23, James sent an email the Council list requesting feedback on several questions related
to meeting planning. The attached document provides an overview of responses to the following questions:
</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">(1) Do we prefer a Single or Split Constituency Day?</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">(2) What is the right number of High Interest Topics (HIT)? The current Block Schedule drafts contain five HIT sessions.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">(3) Any thoughts on the best way to solicit topics for HIT sessions, and how to choose the top 5?</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">(4) Similarly, any thoughts on how to address the inevitable conflicts between working sessions and HITs?</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">(5) Any other specific feedback you’d like us to bring to the SO/AC meeting</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Rubens, Michele, Donna, Rafik, Ed and Carlos provided responses to the above questions. Please reference the attached for full text of the comments, but staff notes a few common threads in the
responses that may feed into further discussion in the Council: </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span style="color:black">-</span><span style="font-size:7.0pt;font-family:"Times New Roman";color:black">
</span><span style="font-size:11.0pt;color:black">There were several responses supporting a single constituency day. Rubens, Michele, and Rafik supported a single constituency day.
</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span style="color:black">-</span><span style="font-size:7.0pt;font-family:"Times New Roman";color:black">
</span><span style="font-size:11.0pt;color:black">Several responses supported either reducing the number of HIT sessions or rethinking the HIT concept. Ed suggested having a single HIT. Rubens supported having 1 or 2 at most. Rafik suggested 3. Michele and
Donna recommended taking a step back to look more broadly at goals around the HIT concept and then planning accordingly.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span style="color:black">-</span><span style="font-size:7.0pt;font-family:"Times New Roman";color:black">
</span><span style="font-size:11.0pt;color:black">Rubens, Ed, and Carlos all supported the notion that when in doubt, make meeting A more like meeting B than meeting C.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">The issue of scheduling was also raised in the Council session in Hyderabad (transcript here:
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__schd.ws_hosted-5Ffiles_icann572016_c8_I57-2520HYD-5FMon07Nov2016-2DGNSO-2520Public-2520Meeting-25202-2Den.pdf&d=DgMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mBQzlSaM6eYCHFBU-v48zs-QSrjHB0aWmHuE4X4drzI&m=xYqYxeFPFwaxxz6gD3BYlivY7Par8rFxQ6dost3KjiY&s=mRlwIZE-amr865Sh1VuCurmKFR2h-kS7oPCyhmoDdB8&e=">
http://schd.ws/hosted_files/icann572016/c8/I57%20HYD_Mon07Nov2016-GNSO%20Public%20Meeting%202-en.pdf[schd.ws]</a>).
</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Several themes came up in the discussion, including:</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span style="color:black">-</span><span style="font-size:7.0pt;font-family:"Times New Roman";color:black">
</span><span style="font-size:11.0pt;color:black">Improving communication during the planning process</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span style="color:black">-</span><span style="font-size:7.0pt;font-family:"Times New Roman";color:black">
</span><span style="font-size:11.0pt;color:black">Revisiting the rubric used for scheduling: take a step back, clarify and prioritize objectives for ICANN meetings, develop schedule based on priorities to use the time effectively</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span style="color:black">-</span><span style="font-size:7.0pt;font-family:"Times New Roman";color:black">
</span><span style="font-size:11.0pt;color:black">Focusing meetings on ICANN’s core, substantive work</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span style="color:black">-</span><span style="font-size:7.0pt;font-family:"Times New Roman";color:black">
</span><span style="font-size:11.0pt;color:black">Managing and (to the extent possible) avoiding critical scheduling conflicts</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span style="color:black">-</span><span style="font-size:7.0pt;font-family:"Times New Roman";color:black">
</span><span style="font-size:11.0pt;color:black">Avoiding duplication of content across sessions</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span style="color:black">-</span><span style="font-size:7.0pt;font-family:"Times New Roman";color:black">
</span><span style="font-size:11.0pt;color:black">Scheduling sessions in a way that maximizes productivity and does not overload participants</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Please note that the above is not intended to be a full summary. It highlights some of the points that have been raised to support further discussion.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Kind regards,</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Emily </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;color:black">Emily Barabas </span>
</b><span style="font-size:11.0pt;color:black">| Policy Specialist</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;color:black">ICANN</span></b><span style="font-size:11.0pt;color:black"> | Internet Corporation for Assigned Names and Numbers</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Email: emily.barabas@icann.org | Phone: +31 (0)6 84507976</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-family:"Times New Roman";color:black">
<hr size="1" width="100%" noshade="" style="color:#A0A0A0" align="center">
</span></div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Times New Roman";color:black">No virus found in this message.<br>
Checked by AVG - <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.avg.com&d=DgMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mBQzlSaM6eYCHFBU-v48zs-QSrjHB0aWmHuE4X4drzI&m=xYqYxeFPFwaxxz6gD3BYlivY7Par8rFxQ6dost3KjiY&s=gemHi8vOTFBbCIzEPtCS2bAHzPKLBSQoEpLk4_43ZhY&e=">
www.avg.com[avg.com]</a><br>
Version: 2016.0.7859 / Virus Database: 4664/13314 - Release Date: 10/30/16<br>
Internal Virus Database is out of date.</span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>