<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=us-ascii">
<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:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:10.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
color:#993366;}
span.EmailStyle24
{mso-style-type:personal-reply;
color:#003300;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#003300">The list rejected the JAS Final Report as requiring moderator approval because the file is so big. I am forwarding this message with a modified file showing the JAS summary recommendations (not the full report).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#003300">Anne<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#003300"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> Aikman-Scalese, Anne
<br>
<b>Sent:</b> Wednesday, September 18, 2019 4:37 PM<br>
<b>To:</b> 'Jeff Neuman' <jeff.neuman@comlaude.com>; 'gnso-newgtld-wg@icann.org' <gnso-newgtld-wg@icann.org><br>
<b>Subject:</b> GNSO Council Letter to ICANN Board on NCAP-SubPro Dependencies<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#993366">Hi Jeff and Cheryl,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#993366">Regarding Monday’s call on name collisions, I have the following comments.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#993366">1. There seemed to be a lot of discussion about JAS having asserted that the system they recommended “worked”. In this regard, the WG has not actually had a substantive discussion on the harm associated with
name collisions. <u>The only reporting requirement from the 2012 round was to report to ICANN any instances that involved a threat to human life</u>. As we know, that is not the only risk posed by name collisions. The risks include the following as detailed
in the attached ICANN advice to IT Professionals (see pages 6-7 of the attachment):<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="color:#993366">Para 2.1</span></b><span style="color:#993366"> – Direction to Unexpected Websites – and interception by malicious actors (which security certificates may not be adequate to prevent), allowing access to sensitive
information and/or allowing the malicious actor to install dangerous code on the user’s computer.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="color:#993366">Para 2.2</span></b><span style="color:#993366"> - Direction of Email to the Wrong Recipients<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="color:#993366">Para 2.3</span></b><span style="color:#993366"> – Security Reductions
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#993366">In the attached JAS Final Report that Jeff and Rubens referenced, Recommendation 14 states as follows:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><img width="1300" height="188" style="width:13.5416in;height:1.9583in" id="Picture_x0020_1" src="cid:image001.png@01D56E3F.2B39F030" alt="cid:image001.png@01D56E3F.2B39F030"><span style="color:#993366"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#993366">Assessing these dangers is a critical part of NCAP Study 1 – to define the harm – and that has to happen in order to have an intelligent discussion of the topic. The NCAP has a half day meeting in Montreal on
Friday afternoon November 1. I am sure Sub Pro WG members are welcome. And I know Jeff assured the NCAP Discussion Group that he joined the Discussion Group for the purpose of coordinating policy with them.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#993366">2. Re the IPC position, just to clarify, the IPC consensus was to defer to NCAP if NCAP recommendations are ready in time for launch. Given that we project a couple of years before the framework for launch
can be in place, it seems reasonable to expect that we could at least develop some sort of testing mechanism for DO NOT APPLY and the Work Track 4 risk categories prior to launch, either via NCAP or an independent advisor. Jeff and Cheryl’s additions to the
GNSO Council letter to the Board should be helpful in this regard. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#993366">Anne<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#993366"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> Aikman-Scalese, Anne
<br>
<b>Sent:</b> Tuesday, September 10, 2019 9:34 PM<br>
<b>To:</b> Jeff Neuman <<a href="mailto:jeff.neuman@comlaude.com">jeff.neuman@comlaude.com</a>>;
<a href="mailto:gnso-newgtld-wg@icann.org">gnso-newgtld-wg@icann.org</a><br>
<b>Subject:</b> RE: FOR REVIEW: Draft GNSO Council Letter to ICANN Board on NCAP-SubPro Dependencies<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Hi Jeff and Cheryl,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks for sending. Two quick comments:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">(1) the word “including” in b) seems to be missing a letter
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">(2) In this draft, can we please ask about the pending discussion in relation to the development of a “DO NOT APPLY” list? (The sooner the NCAP develops a methodology for that, the better off we all are.)
I have not seen a specific reference to a method for testing as to “DO NOT APPLY” or very high risk strings in Study 1 and so the timing there is a bit concerning. ALAC points out we could take a bunch of applications and then not delegate until that work
is done. I have always thought and always commented that there should be a way for an applicant to test a string for name collision issues without having to pay the whole application fee and put all the effort into an application and business plan only to
find it’s a “no go”. We need to be asking about a gating mechanism on this issue to save people a lot of time and trouble. If that gating mechanism were developed during the time the AGB is being written, then that might prove a way forward to coordinate
the timing.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Many thanks for putting this together. I believe the Board commented that there was an “opportunity for collaboration” with NCAP and an ability to work out the scheduling so that maybe their reply (in line with
the public comment filed by the Board). But it never hurts to clarify.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Anne<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> Gnso-newgtld-wg <</span><a href="mailto:gnso-newgtld-wg-bounces@icann.org"><span style="font-size:11.0pt">gnso-newgtld-wg-bounces@icann.org</span></a><span style="font-size:11.0pt">>
<b>On Behalf Of </b>Jeff Neuman<br>
<b>Sent:</b> Tuesday, September 10, 2019 7:47 PM<br>
<b>To:</b> </span><a href="mailto:gnso-newgtld-wg@icann.org"><span style="font-size:11.0pt">gnso-newgtld-wg@icann.org</span></a><span style="font-size:11.0pt"><br>
<b>Subject:</b> [Gnso-newgtld-wg] FW: FOR REVIEW: Draft GNSO Council Letter to ICANN Board on NCAP-SubPro Dependencies<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><strong><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black">[EXTERNAL]</span></strong><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black"><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt">All,<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">We just wanted to forward this note to the SubPro PDP Full Working Group. Cheryl and I were asked by the GNSO Council Leadership to give our thoughts to them about the attached draft letter from the Council
to the ICANN Board. We provided this feedback and as you can see we made it clear that the redlines are from Cheryl and I and not the Working Group.<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">Please let us know if you have any questions.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Jeff Neuman and Cheryl Langdon-Orr</span></b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> Jeff Neuman <</span><a href="mailto:jeff.neuman@comlaude.com"><span style="font-size:11.0pt">jeff.neuman@comlaude.com</span></a><span style="font-size:11.0pt">>
<br>
<b>Sent:</b> Tuesday, September 10, 2019 10:44 PM<br>
<b>To:</b> Drazek, Keith <</span><a href="mailto:kdrazek@verisign.com"><span style="font-size:11.0pt">kdrazek@verisign.com</span></a><span style="font-size:11.0pt">>; Cheryl Langdon-Orr (</span><a href="mailto:langdonorr@gmail.com"><span style="font-size:11.0pt">langdonorr@gmail.com</span></a><span style="font-size:11.0pt">)
(</span><a href="mailto:langdonorr@gmail.com"><span style="font-size:11.0pt">langdonorr@gmail.com</span></a><span style="font-size:11.0pt">) <</span><a href="mailto:langdonorr@gmail.com"><span style="font-size:11.0pt">langdonorr@gmail.com</span></a><span style="font-size:11.0pt">>;
Pam Little <</span><a href="mailto:pam.little@alibaba-inc.com"><span style="font-size:11.0pt">pam.little@alibaba-inc.com</span></a><span style="font-size:11.0pt">>;
</span><a href="mailto:rafik.dammak@gmail.com"><span style="font-size:11.0pt">rafik.dammak@gmail.com</span></a><span style="font-size:11.0pt"><br>
<b>Cc:</b> </span><a href="mailto:gnso-secs@icann.org"><span style="font-size:11.0pt">gnso-secs@icann.org</span></a><span style="font-size:11.0pt">;
</span><a href="mailto:gnso-chairs@icann.org"><span style="font-size:11.0pt">gnso-chairs@icann.org</span></a><span style="font-size:11.0pt">; Steve Chan <</span><a href="mailto:steve.chan@icann.org"><span style="font-size:11.0pt">steve.chan@icann.org</span></a><span style="font-size:11.0pt">>;
Emily Barabas <</span><a href="mailto:emily.barabas@icann.org"><span style="font-size:11.0pt">emily.barabas@icann.org</span></a><span style="font-size:11.0pt">>; Julie Hedlund <</span><a href="mailto:julie.hedlund@icann.org"><span style="font-size:11.0pt">julie.hedlund@icann.org</span></a><span style="font-size:11.0pt">>;
Jeff Neuman <</span><a href="mailto:jeff.neuman@comlaude.com"><span style="font-size:11.0pt">jeff.neuman@comlaude.com</span></a><span style="font-size:11.0pt">><br>
<b>Subject:</b> RE: FOR REVIEW: Draft GNSO Council Letter to ICANN Board on NCAP-SubPro Dependencies<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Dear Keith, Pam and Rafik,<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">Please find enclosed Cheryl and my redlines to the draft letter. We do not believe the substance of the letter has been changed at all, but rather just added some more specificity. This letter contains only
the comments of Cheryl and I and not the Subsequent Procedures Working Group. <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">There are so many people making so many arguments and even if the Board says that there are “dependencies”, I think they need to be specific as to which exact step is the completion of the NCAP work dependent
on. What is the exact point where we cannot move forward. Some people say the Board cannot accept the final policy without this work being done. Some say the policy can be completed, but implementation work cannot be completed prior to the NCAP finishing.
Some say that can complete but we cannot complete the AGB. Some say we can complete that but we cannot announce the new round. Some say we can announce but cannot accept applications. Some say we can do it all but not delegate. And finally some say we
can delegate and use existing name collision model until NCAP states otherwise.<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">We hope this makes sense and please forward to the GNSO Council for its consideration.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><br>
Thanks again for reaching out to us. We are going to forward this correspondence chain to the Full Working Group as well.<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">Best regards,<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"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Jeff Neuman and Cheryl Langdon-Orr<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Subsequent Procedures Co-Chairs<o:p></o:p></span></b></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"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Jeff Neuman</span></b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Senior Vice President <o:p></o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Com Laude | Valideus</span></b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">D: +1.703.635.7514<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">E:
</span><a href="mailto:jeff.neuman@comlaude.com"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">jeff.neuman@comlaude.com</span></a><u><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#0563C1"><o:p></o:p></span></u></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> Drazek, Keith <</span><a href="mailto:kdrazek@verisign.com"><span style="font-size:11.0pt">kdrazek@verisign.com</span></a><span style="font-size:11.0pt">>
<br>
<b>Sent:</b> Monday, September 9, 2019 6:48 PM<br>
<b>To:</b> Jeff Neuman <</span><a href="mailto:jeff.neuman@comlaude.com"><span style="font-size:11.0pt">jeff.neuman@comlaude.com</span></a><span style="font-size:11.0pt">>; Cheryl Langdon-Orr (</span><a href="mailto:langdonorr@gmail.com"><span style="font-size:11.0pt">langdonorr@gmail.com</span></a><span style="font-size:11.0pt">)
(</span><a href="mailto:langdonorr@gmail.com"><span style="font-size:11.0pt">langdonorr@gmail.com</span></a><span style="font-size:11.0pt">) <</span><a href="mailto:langdonorr@gmail.com"><span style="font-size:11.0pt">langdonorr@gmail.com</span></a><span style="font-size:11.0pt">><br>
<b>Cc:</b> </span><a href="mailto:gnso-secs@icann.org"><span style="font-size:11.0pt">gnso-secs@icann.org</span></a><span style="font-size:11.0pt">;
</span><a href="mailto:gnso-chairs@icann.org"><span style="font-size:11.0pt">gnso-chairs@icann.org</span></a><span style="font-size:11.0pt"><br>
<b>Subject:</b> FW: FOR REVIEW: Draft GNSO Council Letter to ICANN Board on NCAP-SubPro Dependencies<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Jeff/Cheryl,<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">FYI, attached is the draft Council letter to the Board on NCAP and SubPro. This has been sent to the Council list for consideration and comment.<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">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Keith<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> council <</span><a href="mailto:council-bounces@gnso.icann.org"><span style="font-size:11.0pt">council-bounces@gnso.icann.org</span></a><span style="font-size:11.0pt">>
<b>On Behalf Of </b>Drazek, Keith via council<br>
<b>Sent:</b> Monday, September 09, 2019 3:47 PM<br>
<b>To:</b> </span><a href="mailto:council@gnso.icann.org"><span style="font-size:11.0pt">council@gnso.icann.org</span></a><span style="font-size:11.0pt"><br>
<b>Cc:</b> </span><a href="mailto:gnso-secs@icann.org"><span style="font-size:11.0pt">gnso-secs@icann.org</span></a><span style="font-size:11.0pt"><br>
<b>Subject:</b> [EXTERNAL] [council] FOR REVIEW: Draft GNSO Council Letter to ICANN Board on NCAP-SubPro Dependencies<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Hi all,<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">Attached for your review is a draft letter from the GNSO Council to the ICANN Board concerning dependencies between the NCAP and Subsequent Procedures PDP.<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">Please review and advise if you have any comments or questions.<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">We can discuss on the list and this will be included on the agenda for our 19 September GNSO Council meeting.<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">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Keith<o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the
intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that the Com Laude Group does not accept any
responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of
its member entities. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company
registered in England and Wales with company number 06181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176, having its registered office at 33 Melville
Street, Edinburgh, Lothian, EH3 7JF Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, headquartered at 1751 Pinnacle Drive, Suite 600, McLean, VA 22102, USA; Com Laude (Japan) Corporation, a company registered in Japan having its registered office
at Suite 319,1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan. For further information see
</span><a href="https://comlaude.com" target="_blank"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">www.comlaude.com</span></a><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<o:p></o:p></span></p>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message
or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying
to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.
<br>
</font>
</body>
</html>