<div><div dir="auto">Since we are all providing unavailbilities, I am unavailable the week of the 21st Jan. </div></div><div dir="auto"><br></div><div dir="auto">Agreed that January generally would be better than December, and I would agree that an EMEA location may be best all considering. </div><div dir="auto"><br></div><div dir="auto">Alan </div><div dir="auto"><br></div><div><br><div class="gmail_quote"><div dir="ltr">On Mon 29 Oct 2018 at 11:17, Thomas Rickert <epdp@gdpr.ninja> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space">Hi Kurt, all,<div>Let me join those who are in favor of holding a meeting in Jan. I have a commitment in Germany I cannot move on Jan 15th, so I might need to join remotely if the meeting is in that week. We have not yet discussed how long the meeting shall be, so the later in the week, the higher the chances I can be with you throughout the entire meeting. I would be ok with traveling on Wed, meeting Thurs to Sat as well. The last two weeks of Jan would work for me entirely.</div><div><br></div><div>As regards location, I would really defer to staff and our leadership to make a decision taking into account cost efficiency and potential synergies with other meetings. As you can see from my comments above, I as many others have limitations affecting their availability and I am happy to join remotely if need be.</div><div><br></div><div>Best,</div><div>Thomas</div></div><div style="word-wrap:break-word;line-break:after-white-space"><div><br></div><div><br></div><div><br></div><div><br><div><br><blockquote type="cite"><div>Am 26.10.2018 um 08:48 schrieb Kurt Pritz <<a href="mailto:kurt@kjpritz.com" target="_blank">kurt@kjpritz.com</a>>:</div><br class="m_4247603800114561682Apple-interchange-newline"><div><div style="word-wrap:break-word;line-break:after-white-space">Hi Everyone:<div><br></div><div>Thank you again for your time, effort and thought during the ICANN meeting. While others were visiting the various great sites that Barcelona has to offer, we were all not visiting the various great sites that Barcelona has to offer.</div><div><br></div><div>Yesterday, I met with Nick Tomasso who heads the ICANN meetings team to develop some options for the next face-to-face meeting. At various times during the past week, many of you approached me with the following points:</div><div><ul class="m_4247603800114561682MailOutline"><li>Our results are significantly better in a face-to-face format</li><li>The proverbial clock is ticking</li><li>We should strive to maintain the momentum we have, therefore</li><li>We should hold our next meeting as soon as possible.</li></ul><div><br></div></div><div>With that in mind, Nick said he could support the following two options, a meeting</div><div><ul class="m_4247603800114561682MailOutline"><li>In the first or second week in December</li><li>In the second or third week of January</li></ul><div> </div></div><div>[Meetings less than 90 days away require Göran’s approval, but Nick believes he can obtain this. Nick is checking on venues with which he is familiar in Brussels now, although the meeting location is not certain.]</div><div><br></div><div>I am of two minds on this but do have an opinion and would appreciate your feedback over the next few days so that I can get back to Nick the first of next week. </div><div><br></div><div>1) The January meeting is more or less timed for us to take into account the first round of public comment.</div><div><br></div><div>2) Te December meeting allows us to keep working after the initial report is issued (or to wrap up the initial report in the worse case). </div><div><br></div><div>I think the December meeting is the better option for us. We are not going to stand down after the initial report is issued. There is a lot of work to be done. It is better, I think, to meet and consider unsettled issues, rather than meet to discuss the effect of public comment. If we are serious about finishing on time, I don’t think we can stop. So despite the inconvenience (and it will be very inconvenient for me), I think we should meet sooner rather than later. </div><div><br></div><div>Of course, this all depends on the ICANN meetings team pulling this off, which is no small feat, </div><div><br></div><div>Let me know your thoughts, I will write to Nick on Tuesday. </div><div><br></div><div>Best regards,</div><div><br></div><div>Kurt</div><div><br></div></div>_______________________________________________<br>Gnso-epdp-team mailing list<br><a href="mailto:Gnso-epdp-team@icann.org" target="_blank">Gnso-epdp-team@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a></div></blockquote></div><br></div></div>_______________________________________________<br>
Gnso-epdp-team mailing list<br>
<a href="mailto:Gnso-epdp-team@icann.org" target="_blank">Gnso-epdp-team@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a></blockquote></div></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><table style="padding:0px;margin:10px 0;border:none"><tbody><tr><td style="vertical-align:middle;padding:0px 7px 0px 0px"><a href="http://donuts.domains" rel="nofollow" target="_blank"><img alt="Donuts Inc." height="75" src="https://storage.googleapis.com/signaturesatori/customer-C02zzlf7k/images/-54f9d8ac97e7f575bf497d10ac1f1aafafddf8afceab5f269d49034f01b3217b.png" width="75"></a></td><td style="vertical-align:middle;padding:0px 7px 0px 0px;text-align:left">
<div style="font-family:'tahoma',sans-serif;font-size:14px;line-height:17px;font-weight:bold;color:black"><span style="font-size:12px"><span style="font-family:'arial','helvetica',sans-serif"><span style="color:rgb(51,51,51)">Alan Woods</span></span></span></div>
<div><span style="font-size:12px"><span style="font-family:'arial','helvetica',sans-serif"><span style="color:#333333">Senior Compliance & Policy Manager, Donuts Inc.</span></span></span>
<hr><span style="font-size:11px"><span style="font-family:'arial','helvetica',sans-serif"><span style="color:#333333">The Victorians, </span></span></span></div><div><font color="#333333" face="arial, helvetica, sans-serif"><span style="font-size:11px">15-18 Earlsfort Terrace<br style="background-color:rgb(34,34,34)">
Dublin 2, County Dublin</span></font><br style="color:rgb(214,214,214);font-family:'open sans';font-size:12px;background-color:rgb(34,34,34)"><font color="#333333" face="arial, helvetica, sans-serif"><span style="font-size:11px">
Ireland</span></font><br>
<span style="font-size:11px"><span style="font-family:'arial','helvetica',sans-serif"></span></span><br>
<span style="line-height:36px"><a href="https://www.facebook.com/donutstlds" rel="nofollow" target="_blank"><img src="http://storage.googleapis.com/signaturesatori/icons/facebook.png"></a> <a href="https://twitter.com/DonutsInc" rel="nofollow" target="_blank"><img src="http://storage.googleapis.com/signaturesatori/icons/twitter.png"></a> </span><a href="https://www.linkedin.com/company/donuts-inc" rel="nofollow" target="_blank"><span style="font-size:14px"><img src="http://storage.googleapis.com/signaturesatori/icons/linkedin.png"></span></a></div>
</td></tr></tbody></table><br>
</div><div><span style="font-size:12pt;font-family:Cambria,serif">Please NOTE: This electronic message, including any attachments, may include privileged, confidential and/or inside information owned by Donuts Inc. . </span><span style="font-size:12pt;font-family:Cambria,serif">Any distribution or use of this communication by anyone other than the intended recipient(s) is strictly prohibited and may be unlawful. If you are not the intended recipient, please notify the sender by replying to this message and then delete it from your system. Thank you.</span><br></div></div></div></div></div></div></div></div></div>