<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 18 Sep 2019, at 20:53, Aikman-Scalese, Anne <<a href="mailto:AAikman@lrrc.com" class="">AAikman@lrrc.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(0, 51, 0);" class="">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 class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(0, 51, 0);" class="">Anne<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(0, 51, 0);" class=""><o:p class=""> </o:p></span></div><div class=""><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="font-size: 11pt;" class="">From:</span></b><span style="font-size: 11pt;" class=""><span class="Apple-converted-space"> </span>Aikman-Scalese, Anne<span class="Apple-converted-space"> </span><br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>Wednesday, September 18, 2019 4:37 PM<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span>'Jeff Neuman' <<a href="mailto:jeff.neuman@comlaude.com" style="color: purple; text-decoration: underline;" class="">jeff.neuman@comlaude.com</a>>; '<a href="mailto:gnso-newgtld-wg@icann.org" style="color: purple; text-decoration: underline;" class="">gnso-newgtld-wg@icann.org</a>' <<a href="mailto:gnso-newgtld-wg@icann.org" style="color: purple; text-decoration: underline;" class="">gnso-newgtld-wg@icann.org</a>><br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>GNSO Council Letter to ICANN Board on NCAP-SubPro Dependencies<o:p class=""></o:p></span></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class="">Hi Jeff and Cheryl,<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class="">Regarding Monday’s call on name collisions, I have the following comments.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class="">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. <span class="Apple-converted-space"> </span></span></div></div></div></blockquote><div><br class=""></div><div><br class=""></div>Because WT4 already had substantive discussions, and interested WG members can either ask questions on this now or refer to WT4 transcripts. </div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class=""><u class="">The only reporting requirement from the 2012 round was to report to ICANN any instances that involved a threat to human life</u>. </span></div></div></div></blockquote><div><br class=""></div>That's not true. The only requirement involving threat to human life was the requirement to act on the report; ICANN received a number of reports, and since 0 of them were about threat to human life, all of them did not include threat to human life. </div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class=""> 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 class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="color: rgb(153, 51, 102);" class="">Para 2.1</span></b><span style="color: rgb(153, 51, 102);" class=""><span class="Apple-converted-space"> </span>– 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 class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="color: rgb(153, 51, 102);" class="">Para 2.2</span></b><span style="color: rgb(153, 51, 102);" class=""><span class="Apple-converted-space"> </span>- Direction of Email to the Wrong Recipients<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="color: rgb(153, 51, 102);" class="">Para 2.3</span></b><span style="color: rgb(153, 51, 102);" class=""><span class="Apple-converted-space"> </span>– Security Reductions</span></div></div></div></blockquote><div><br class=""></div>And that's exactly what controlled interruption was all about: making the collision be noticed by users but without incurring those risks. </div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class=""><o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class="">In the attached JAS Final Report that Jeff and Rubens referenced, Recommendation 14 states as follows:<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span id="cid:image001.png@01D56E3F.2B39F030"><image001.png></span><span style="color: rgb(153, 51, 102);" class=""><o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class="">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. </span></div></div></div></blockquote><div><br class=""></div><div><br class=""></div>Actually not; unfortunately, NCAP disregarded recommendation 14 of the JAS report and failed to include the collision risk in existing gTLD registries (which BTW only has cases known in legacy gTLDs, not in new gTLDs) in its scope, so this problem will still need addressing by someone else. And while this is in our charter, there were no discussions of this subject so far, either in WT4 or WG... so for now, the only thing we can say in the final report is that this is still not discussed. </div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class=""> 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 class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class="">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. <span class="Apple-converted-space"> </span></span></div></div></div></blockquote><div><br class=""></div><div><br class=""></div>The problem is that the testing mechanism and the creation of the DO NOT APPLY list didn't make the cut for a consensus determination, in most part due to IPC and ALAC positions to defer to NCAP. The only items that survived from WT4 discussions were the substantial refund for application that ICANN refuse to sign/delegate due to name collision and the possibility of, on ICANN Org's request or approval, to disable controlled interruption for one or a few labels instead of being a all-or-nothing mechanism. All other discussions ended up in no consensus, so defaulting to 2012 implementation. </div><div><br class=""></div><div><br class=""></div><div>Rubens</div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class=""><o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class="">Anne<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(153, 51, 102);" class=""><o:p class=""> </o:p></span></div><div class=""><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="font-size: 11pt;" class="">From:</span></b><span style="font-size: 11pt;" class=""><span class="Apple-converted-space"> </span>Aikman-Scalese, Anne<span class="Apple-converted-space"> </span><br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>Tuesday, September 10, 2019 9:34 PM<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span>Jeff Neuman <<a href="mailto:jeff.neuman@comlaude.com" style="color: purple; text-decoration: underline;" class="">jeff.neuman@comlaude.com</a>>;<span class="Apple-converted-space"> </span><a href="mailto:gnso-newgtld-wg@icann.org" style="color: purple; text-decoration: underline;" class="">gnso-newgtld-wg@icann.org</a><br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>RE: FOR REVIEW: Draft GNSO Council Letter to ICANN Board on NCAP-SubPro Dependencies<o:p class=""></o:p></span></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">Hi Jeff and Cheryl,<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">Thanks for sending. Two quick comments:<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">(1) the word “including” in b) seems to be missing a letter <o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">(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 class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">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 class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class="">Anne<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="font-size: 11pt;" class="">From:</span></b><span style="font-size: 11pt;" class=""><span class="Apple-converted-space"> </span>Gnso-newgtld-wg <</span><a href="mailto:gnso-newgtld-wg-bounces@icann.org" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">gnso-newgtld-wg-bounces@icann.org</span></a><span style="font-size: 11pt;" class="">><span class="Apple-converted-space"> </span><b class="">On Behalf Of<span class="Apple-converted-space"> </span></b>Jeff Neuman<br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>Tuesday, September 10, 2019 7:47 PM<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span></span><a href="mailto:gnso-newgtld-wg@icann.org" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">gnso-newgtld-wg@icann.org</span></a><span style="font-size: 11pt;" class=""><br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>[Gnso-newgtld-wg] FW: FOR REVIEW: Draft GNSO Council Letter to ICANN Board on NCAP-SubPro Dependencies<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><strong class=""><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class="">[EXTERNAL]</span></strong><span style="font-size: 9pt; font-family: Helvetica, sans-serif;" class=""><o:p class=""></o:p></span></div><div class="MsoNormal" align="center" style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif; text-align: center;"><hr size="2" width="100%" align="center" class=""></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">All,<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">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 class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">Please let us know if you have any questions.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><b class=""><span lang="EN-GB" style="font-size: 9pt; font-family: Arial, sans-serif;" class="">Jeff Neuman and Cheryl Langdon-Orr</span></b><span lang="EN-GB" style="font-size: 9pt; font-family: Arial, sans-serif;" class=""><o:p class=""></o:p></span></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div class=""><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="font-size: 11pt;" class="">From:</span></b><span style="font-size: 11pt;" class=""><span class="Apple-converted-space"> </span>Jeff Neuman <</span><a href="mailto:jeff.neuman@comlaude.com" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">jeff.neuman@comlaude.com</span></a><span style="font-size: 11pt;" class="">><span class="Apple-converted-space"> </span><br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>Tuesday, September 10, 2019 10:44 PM<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span>Drazek, Keith <</span><a href="mailto:kdrazek@verisign.com" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">kdrazek@verisign.com</span></a><span style="font-size: 11pt;" class="">>; Cheryl Langdon-Orr (</span><a href="mailto:langdonorr@gmail.com" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">langdonorr@gmail.com</span></a><span style="font-size: 11pt;" class="">) (</span><a href="mailto:langdonorr@gmail.com" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">langdonorr@gmail.com</span></a><span style="font-size: 11pt;" class="">) <</span><a href="mailto:langdonorr@gmail.com" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">langdonorr@gmail.com</span></a><span style="font-size: 11pt;" class="">>; Pam Little <</span><a href="mailto:pam.little@alibaba-inc.com" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">pam.little@alibaba-inc.com</span></a><span style="font-size: 11pt;" class="">>;<span class="Apple-converted-space"> </span></span><a href="mailto:rafik.dammak@gmail.com" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">rafik.dammak@gmail.com</span></a><span style="font-size: 11pt;" class=""><br class=""><b class="">Cc:</b><span class="Apple-converted-space"> </span></span><a href="mailto:gnso-secs@icann.org" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">gnso-secs@icann.org</span></a><span style="font-size: 11pt;" class="">;<span class="Apple-converted-space"> </span></span><a href="mailto:gnso-chairs@icann.org" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">gnso-chairs@icann.org</span></a><span style="font-size: 11pt;" class="">; Steve Chan <</span><a href="mailto:steve.chan@icann.org" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">steve.chan@icann.org</span></a><span style="font-size: 11pt;" class="">>; Emily Barabas <</span><a href="mailto:emily.barabas@icann.org" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">emily.barabas@icann.org</span></a><span style="font-size: 11pt;" class="">>; Julie Hedlund <</span><a href="mailto:julie.hedlund@icann.org" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">julie.hedlund@icann.org</span></a><span style="font-size: 11pt;" class="">>; Jeff Neuman <</span><a href="mailto:jeff.neuman@comlaude.com" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">jeff.neuman@comlaude.com</span></a><span style="font-size: 11pt;" class="">><br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>RE: FOR REVIEW: Draft GNSO Council Letter to ICANN Board on NCAP-SubPro Dependencies<o:p class=""></o:p></span></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">Dear Keith, Pam and Rafik,<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">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. <span class="Apple-converted-space"> </span><o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">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 class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">We hope this makes sense and please forward to the GNSO Council for its consideration.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><br class="">Thanks again for reaching out to us. We are going to forward this correspondence chain to the Full Working Group as well.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">Best regards,<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><b class=""><span lang="EN-GB" style="font-size: 9pt; font-family: Arial, sans-serif;" class="">Jeff Neuman and Cheryl Langdon-Orr<o:p class=""></o:p></span></b></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><b class=""><span lang="EN-GB" style="font-size: 9pt; font-family: Arial, sans-serif;" class="">Subsequent Procedures Co-Chairs<o:p class=""></o:p></span></b></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><b class=""><span lang="EN-GB" style="font-size: 9pt; font-family: Arial, sans-serif;" class="">Jeff Neuman</span></b><span lang="EN-GB" style="font-size: 9pt; font-family: Arial, sans-serif;" class=""><o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-GB" style="font-size: 9pt; font-family: Arial, sans-serif;" class="">Senior Vice President <o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><b class=""><span lang="EN-GB" style="font-size: 9pt; font-family: Arial, sans-serif;" class="">Com Laude | Valideus</span></b><span lang="EN-GB" style="font-size: 9pt; font-family: Arial, sans-serif;" class=""><o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-GB" style="font-size: 9pt; font-family: Arial, sans-serif;" class="">D: +1.703.635.7514<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-GB" style="font-size: 9pt; font-family: Arial, sans-serif;" class="">E:<span class="Apple-converted-space"> </span></span><a href="mailto:jeff.neuman@comlaude.com" style="color: purple; text-decoration: underline;" class=""><span lang="EN-GB" style="font-size: 9pt; font-family: Arial, sans-serif;" class="">jeff.neuman@comlaude.com</span></a><u class=""><span lang="EN-GB" style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(5, 99, 193);" class=""><o:p class=""></o:p></span></u></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div class=""><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="font-size: 11pt;" class="">From:</span></b><span style="font-size: 11pt;" class=""><span class="Apple-converted-space"> </span>Drazek, Keith <</span><a href="mailto:kdrazek@verisign.com" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">kdrazek@verisign.com</span></a><span style="font-size: 11pt;" class="">><span class="Apple-converted-space"> </span><br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>Monday, September 9, 2019 6:48 PM<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span>Jeff Neuman <</span><a href="mailto:jeff.neuman@comlaude.com" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">jeff.neuman@comlaude.com</span></a><span style="font-size: 11pt;" class="">>; Cheryl Langdon-Orr (</span><a href="mailto:langdonorr@gmail.com" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">langdonorr@gmail.com</span></a><span style="font-size: 11pt;" class="">) (</span><a href="mailto:langdonorr@gmail.com" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">langdonorr@gmail.com</span></a><span style="font-size: 11pt;" class="">) <</span><a href="mailto:langdonorr@gmail.com" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">langdonorr@gmail.com</span></a><span style="font-size: 11pt;" class="">><br class=""><b class="">Cc:</b><span class="Apple-converted-space"> </span></span><a href="mailto:gnso-secs@icann.org" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">gnso-secs@icann.org</span></a><span style="font-size: 11pt;" class="">;<span class="Apple-converted-space"> </span></span><a href="mailto:gnso-chairs@icann.org" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">gnso-chairs@icann.org</span></a><span style="font-size: 11pt;" class=""><br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>FW: FOR REVIEW: Draft GNSO Council Letter to ICANN Board on NCAP-SubPro Dependencies<o:p class=""></o:p></span></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">Jeff/Cheryl,<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">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 class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">Best,<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">Keith<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div class=""><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="font-size: 11pt;" class="">From:</span></b><span style="font-size: 11pt;" class=""><span class="Apple-converted-space"> </span>council <</span><a href="mailto:council-bounces@gnso.icann.org" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">council-bounces@gnso.icann.org</span></a><span style="font-size: 11pt;" class="">><span class="Apple-converted-space"> </span><b class="">On Behalf Of<span class="Apple-converted-space"> </span></b>Drazek, Keith via council<br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>Monday, September 09, 2019 3:47 PM<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span></span><a href="mailto:council@gnso.icann.org" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">council@gnso.icann.org</span></a><span style="font-size: 11pt;" class=""><br class=""><b class="">Cc:</b><span class="Apple-converted-space"> </span></span><a href="mailto:gnso-secs@icann.org" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 11pt;" class="">gnso-secs@icann.org</span></a><span style="font-size: 11pt;" class=""><br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>[EXTERNAL] [council] FOR REVIEW: Draft GNSO Council Letter to ICANN Board on NCAP-SubPro Dependencies<o:p class=""></o:p></span></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">Hi all,<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">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 class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">Please review and advise if you have any comments or questions.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">We can discuss on the list and this will be included on the agenda for our 19 September GNSO Council meeting.<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">Thanks,<o:p class=""></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">Keith<o:p class=""></o:p></span></div><div class="MsoNormal" align="center" style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif; text-align: center;"><span style="font-size: 12pt; font-family: "Times New Roman", serif;" class=""><hr size="2" width="100%" align="center" class=""></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 12pt; font-family: "Times New Roman", serif;" class="">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 class="Apple-converted-space"> </span></span><a href="https://comlaude.com/" target="_blank" style="color: purple; text-decoration: underline;" class=""><span style="font-size: 12pt; font-family: "Times New Roman", serif;" class="">www.comlaude.com</span></a><span style="font-size: 12pt; font-family: "Times New Roman", serif;" class=""><o:p class=""></o:p></span></div></div><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><hr style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><font face="Arial" color="Gray" size="1" style="font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br class="">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.<span class="Apple-converted-space"> </span><br class=""></font><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class=""></span><span id="cid:2B95B127-732F-40A0-A74A-FCE965DDA283"><IT Professionals - name-collision-mitigation-05dec13-en.pdf></span><span id="cid:5ECB1C9C-F077-4379-8E61-C2A7D6915AE1"><JAS Final Report pages Cover through 8 - Summary of Recommendations.pdf></span><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">_______________________________________________</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Gnso-newgtld-wg mailing list</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><a href="mailto:Gnso-newgtld-wg@icann.org" style="color: purple; text-decoration: underline; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">Gnso-newgtld-wg@icann.org</a><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg" style="color: purple; text-decoration: underline; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</a><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">_______________________________________________</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (</span><a href="https://www.icann.org/privacy/policy" style="color: purple; text-decoration: underline; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">https://www.icann.org/privacy/policy</a><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">) and the website Terms of Service (</span><a href="https://www.icann.org/privacy/tos" style="color: purple; text-decoration: underline; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">https://www.icann.org/privacy/tos</a><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</span></div></blockquote></div><br class=""></body></html>