<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Thanks very much Keith,</p>
<p>the revised motion shall have my support.</p>
<p>Best regards</p>
<p>Wolf-Ulrich</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">Am 23.08.2017 um 10:18 schrieb Drazek,
Keith via council:<br>
</div>
<blockquote type="cite"
cite="mid:504F95D0035A264EBB1BFAABAA772B957F32EBB7@BRN1WNEXMBX01.vcorp.ad.vrsn.com">
<meta http-equiv="Context-Type" content="text/html;
charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<div class="WordSection1">
<p class="MsoNormal">Hi all,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">To prepare for our vote on the CCWG-IG
motion this Thursday, here’s where we stand.
</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I’d like to thank both Rafik and
Wolf-Ulrich for their input last week. Rafik and I exchanged
emails again this week and I believe we are in sync.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">As the maker of the motion:</p>
<p class="MsoNormal"> </p>
<ol start="1" type="1">
<li class="MsoNormal">I accept the proposed change of the
withdrawal deadline from ICANN 60 to ICANN 61.</li>
<li class="MsoNormal">I agree that we need some additional
clarity about the expected timeline leading up to ICANN 61,
so the transition can be as seamless as possible. I suggest
we target a GNSO Council meeting mid-way between ICANN 60
and ICANN 61 as the opportunity for the GNSO Council to
review the proposed replacement structure. I’m also support
acknowledging further that the GNSO Council expects a
replacement to be created by ICANN 61.</li>
<li class="MsoNormal">With the extension, ICANN 61 needs to be
the clear date for withdrawal. If we leave wiggle room in
the motion, then the work of finding a replacement will not
have the urgency or attention it requires. We are extending
the date to allow for the necessary work, but I think that
new date needs to be firm. We have all seen how, at ICANN,
“work fills the time and space provided.” We need to avoid
further slippage and set clear expectations for ourselves
and for the other Chartering Organizations.</li>
</ol>
<p class="MsoNormal"> </p>
<p class="MsoNormal">As such, I’ve attached updated motion
language that I believe addresses the points raised to date.
</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">James, as the seconder of the motion, do
you concur or have any concerns?</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Regards,</p>
<p class="MsoNormal">Keith</p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
council mailing list
<a class="moz-txt-link-abbreviated" href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/council">https://mm.icann.org/mailman/listinfo/council</a>
</pre>
</blockquote>
<br>
</body>
</html>