<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="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<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:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">Agree with you both.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">Updates are of course useful, but can be pre-meeting webinars/pre-reads/perhaps a 2 minute overview with one slide as an intro for the F2F. Then we need to know projected timelines,
any issues/problems/blockages and everything Michele lists. We’re supposed to have an overview of process including concerns and of course we do have to meet physically as we’re supposed to help as well as represent!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">Thanks<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">Marie<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> council <council-bounces@gnso.icann.org>
<b>On Behalf Of </b>Michele Neylon - Blacknight<br>
<b>Sent:</b> Tuesday, August 28, 2018 10:53 AM<br>
<b>To:</b> Heather Forrest <haforrestesq@gmail.com>; GNSO Council List <council@gnso.icann.org><br>
<b>Subject:</b> Re: [council] PDP updates for ICANN63<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Heather<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">My own thoughts are that any “updates” should be more of a dialogue.
<o:p></o:p></p>
<p class="MsoNormal">Is there something happening within the PDP that we need to know about?<o:p></o:p></p>
<p class="MsoNormal">Is action from us required?<o:p></o:p></p>
<p class="MsoNormal">Do they need something from us?<o:p></o:p></p>
<p class="MsoNormal">Do they need something from the various SGs etc?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I agree about duplication <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Michele<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="color:black">--<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Mr Michele Neylon<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Blacknight Solutions<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Hosting, Colocation & Domains<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><a href="https://www.blacknight.com/">https://www.blacknight.com/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><a href="https://blacknight.blog/">https://blacknight.blog/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Intl. +353 (0) 59 9183072<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Direct Dial: +353 (0)59 9183090<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Personal blog: <a href="https://michele.blog/">
https://michele.blog/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Some thoughts: <a href="https://ceo.hosting/">
https://ceo.hosting/</a> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">-------------------------------<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:black">Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-IE" style="font-size:12.0pt;color:black">From:
</span></b><span lang="EN-IE" style="font-size:12.0pt;color:black">council <<a href="mailto:council-bounces@gnso.icann.org">council-bounces@gnso.icann.org</a>> on behalf of Heather Forrest <<a href="mailto:haforrestesq@gmail.com">haforrestesq@gmail.com</a>><br>
<b>Date: </b>Tuesday 28 August 2018 at 08:03<br>
<b>To: </b>GNSO Council List <<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>><br>
<b>Subject: </b>[council] PDP updates for ICANN63<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-IE"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-IE">Dear Council colleagues, <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-IE"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-IE">As we enter the final stretch of pre-ICANN63 planning I would like to do a bit of strategic thinking about how we prepare for PDP work in Barcelona.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-IE"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-IE">We have over the years tried two methods - devoting time in the Council weekend workshop to an update from each of our live PDPs, and the more recent alternative of a pre-public meeting GNSO policy webinar. There is also,
I should add here for context, a broader ICANN policy webinar that occurs prior to public meetings in which the GNSO participates, as do other SO/ACs.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-IE"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-IE">The question here is how best/most useful/most efficient to update on our PDPs: on the ground in Barcelona, or advance by webinar? My principal feedback to staff to this point has been that while I think it's very helpful
to have the updates before we hit the ground at a f2f, it seems to duplicate efforts to hold both a generic policy webinar
<i>and </i>a GNSO specific policy webinar.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-IE"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-IE">Your thoughts very much appreciated!<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-IE"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-IE">Heather<o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>