<div><div dir="auto">I agree with Volker and with proposition stated by Jeff.</div></div><div dir="auto"><br></div><div dir="auto">Greg</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Aug 18, 2019 at 9:05 AM <a href="mailto:lists@christopherwilkinson.eu">lists@christopherwilkinson.eu</a> <<a href="mailto:lists@christopherwilkinson.eu">lists@christopherwilkinson.eu</a>> 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"><div style="word-wrap:break-word;line-break:after-white-space">Dear Jeff:<div><br></div><div>1.<span class="m_-6788390912272668568Apple-tab-span" style="white-space:pre-wrap"> </span>My PROPOSAL is limited to Top Level domains. This is because (a) I initiated the proposal in WT5 which is limited to geo-TLDs, and (b) by analogy with ISO 3166 alpha3 codes, ISO 4217 codes are all derived from ISO 3166 alpha2 codes. They should both be protected at least on a par with each other. (The currency codes are of greater economic significance than the three letter country codes.)</div><div><br></div><div>2.<span class="m_-6788390912272668568Apple-tab-span" style="white-space:pre-wrap"> </span>Currency codes as SLDs? Sooner or later the question will arise, by analogy with the alpha2 country codes as SLDs, and the acronyms of the international organisations. For there is also scope for confusion and misrepresentation.</div><div>But that is not part of my proposal at the Top Level.</div><div><br></div><div>3.<span class="m_-6788390912272668568Apple-tab-span" style="white-space:pre-wrap"> </span>The topic ‘Reserved Names’ is a black box as far as I am concerned. Last time I looked, it was in fact about strings that are ‘Unavailable’ for technical reasons. (e.g. IANA etc) There is an error in the vocabulary that was pointed out during our last call.</div><div><br></div><div>Best regards</div><div><br></div><div>Christopher</div><div><br></div><div>PS: I shall not be able to join the call on Monday evening for a family visit here.</div></div></div><div style="word-wrap:break-word;line-break:after-white-space"><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>On 14 Aug 2019, at 21:18, Jeff Neuman <<a href="mailto:jeff.neuman@comlaude.com" target="_blank">jeff.neuman@comlaude.com</a>> wrote:</div><br class="m_-6788390912272668568Apple-interchange-newline"><div><div class="m_-6788390912272668568WordSection1" style="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;text-decoration:none"><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Christopher,<u></u><u></u></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Just to clarify, the proposal you have made is for the top level not SLD level, correct? The topic “Reserved Names” covers both subjects. I just want to make sure I fully understand your proposal.<u></u><u></u></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><b><span lang="EN-GB" style="font-size:9pt;font-family:Arial,sans-serif">Jeffrey J. Neuman</span></b><span lang="EN-GB" style="font-size:9pt;font-family:Arial,sans-serif"><br>Senior Vice President<u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><b><span lang="EN-GB" style="font-size:9pt;font-family:Arial,sans-serif">Com Laude | Valideus<br></span></b><span lang="EN-GB" style="font-size:9pt;font-family:Arial,sans-serif"><a href="https://www.google.com/maps/search/1751+Pinnacle+Drive+,+Suite+600+Mclean+,+VA+22102+UNITED+STATES?entry=gmail&source=g">1751 Pinnacle Drive , Suite 600</a><br><a href="https://www.google.com/maps/search/1751+Pinnacle+Drive+,+Suite+600+Mclean+,+VA+22102+UNITED+STATES?entry=gmail&source=g">Mclean , VA 22102</a><br><a href="https://www.google.com/maps/search/1751+Pinnacle+Drive+,+Suite+600+Mclean+,+VA+22102+UNITED+STATES?entry=gmail&source=g">UNITED STATES</a><br> <br>T: +1.703.635.7514<br>M: +1.202.549.5079<br><br><u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-GB" style="font-family:Arial,sans-serif"> <u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-GB" style="font-size:8pt;font-family:Arial,sans-serif"><u></u> <u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-GB" style="font-size:8pt;font-family:Arial,sans-serif">CONFIRMATION OF ORDERS: Please note that we always confirm receipt of orders. To assist us in identifying orders, please use the word ORDER in the subject line of your email. If you have sent us an order and have not received confirmation on the same working day (PST) it is possible that your order has not been received or has been trapped by our spam filter. In this case, please contact your client manager or<span class="m_-6788390912272668568Apple-converted-space"> </span><a href="mailto:admin@comlaude.com" style="color:purple;text-decoration:underline" target="_blank">admin@comlaude.com</a><span class="m_-6788390912272668568Apple-converted-space"> </span>for confirmation that the order has been received and is being processed. Thank you.<u></u><u></u></span></div></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div><div><div style="border-style:solid none none;border-top-width:1pt;border-top-color:rgb(225,225,225);padding:3pt 0in 0in"><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><b>From:</b><span class="m_-6788390912272668568Apple-converted-space"> </span><a href="mailto:lists@christopherwilkinson.eu" target="_blank">lists@christopherwilkinson.eu</a> <<a href="mailto:lists@christopherwilkinson.eu" target="_blank">lists@christopherwilkinson.eu</a>><span class="m_-6788390912272668568Apple-converted-space"> </span><br><b>Sent:</b><span class="m_-6788390912272668568Apple-converted-space"> </span>Wednesday, August 14, 2019 10:27 AM<br><b>To:</b><span class="m_-6788390912272668568Apple-converted-space"> </span>Jeff Neuman <<a href="mailto:jeff.neuman@comlaude.com" target="_blank">jeff.neuman@comlaude.com</a>><br><b>Cc:</b><span class="m_-6788390912272668568Apple-converted-space"> </span>Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" target="_blank">julie.hedlund@icann.org</a>>; <a href="mailto:gnso-newgtld-wg@icann.org" target="_blank">gnso-newgtld-wg@icann.org</a><br><b>Subject:</b><span class="m_-6788390912272668568Apple-converted-space"> </span>Re: CURRENCY CODES: WAS RE: [Gnso-newgtld-wg] Proposed agenda - New gTLD Subsequent Procedures PDP WG - 12 August 2019 at 15:00 UTC<u></u><u></u></div></div></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><br><br><u></u><u></u></div><blockquote style="margin-top:5pt;margin-bottom:5pt"><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">On 14 Aug 2019, at 16:16, Jeff Neuman <<a href="mailto:jeff.neuman@comlaude.com" style="color:purple;text-decoration:underline" target="_blank">jeff.neuman@comlaude.com</a>> wrote:<u></u><u></u></div></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><span class="m_-6788390912272668568apple-converted-space"> ></span>Reserving strings should always be the exception and not the rule in terms of handling issues.<u></u><u></u></div></div></blockquote><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">In my experience, that is an unrealistic idea,<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">If and when Geo-TLDs are delegated, there will be.a massive demand for reservation of SLDs for relevant locations.<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Whether this is handled by reservation or by sunrise, remains to be discussed.<u></u><u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">CW<u></u><u></u></div></div><div style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></div></div></div><hr style="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;text-decoration:none"><span style="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;text-decoration:none;float:none;display:inline!important">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 <a href="https://www.google.com/maps/search/28-30+Little+Russell+Street,+London,+WC1A+2HN+England?entry=gmail&source=g">28-30 Little Russell Street, London, WC1A 2HN England</a>; Valideus Limited, a company registered in England and Wales with company number 06181291 and registered office at <a href="https://www.google.com/maps/search/28-30+Little+Russell+Street,+London,+WC1A+2HN+England?entry=gmail&source=g">28-30 Little Russell Street, London, WC1A 2HN England</a>; Demys Limited, a company registered in Scotland with company number SC197176, having its registered office at <a href="https://www.google.com/maps/search/33+Melville+Street,+Edinburgh?entry=gmail&source=g">33 Melville Street, Edinburgh</a>, Lothian, EH3 7JF Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, headquartered at <a href="https://www.google.com/maps/search/1751+Pinnacle+Drive,+Suite+600,+McLean,+VA+22102,+USA?entry=gmail&source=g">1751 Pinnacle Drive, Suite 600, McLean, VA 22102, USA</a>; 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="m_-6788390912272668568Apple-converted-space"> </span></span><a href="https://comlaude.com/" 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;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">www.comlaude.com</a></div></blockquote></div><br></div></div></div>_______________________________________________<br>
Gnso-newgtld-wg mailing list<br>
<a href="mailto:Gnso-newgtld-wg@icann.org" target="_blank">Gnso-newgtld-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</a><br>
_______________________________________________<br>
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 (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). 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.</blockquote></div></div>