<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
@font-face
{font-family:Menlo-Regular;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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">David,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The GNSO is responsible for setting all policy with respect to the gTLD namespace. This issue is no different that the GNSO Subsequent Procedures group looking at the policy behind reserving 2 characters for the ccTLDs which it did in
2008 and again is in the process of reviewing. It is the GNSO (and the ICANN community) that decided to reserve the 2 characters for the use of the ccTLDs using the ISO3166 list. It is the GNSO community that will be affirming that in SubPro.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">But just because it affirmed the right of ccTLDs on the ISO list to use these 2 character codes, does not mean it reserved the right for anyone else to use the 2 character labels (including the IETF). In fact, the SubPro group is in discussions
to allow 2 character registrations using a number and a letter (ex. .3d or .3M, O2, etc. You will have seen that in the Initial Report.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So, it is through the policy process that we reserved the right for ccTLDs to register 2 character codes. Similarly it should be through the ICANN policy process that non-ccTLDs may be able to use 2 character codes that correspond to an
ISO code even if the ccTLD does not want it (or cant get it).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I see no difference. And at the end of the day, this is exactly the type of thing that should be discussed within the ICANN community and not outside of it. Why is their reluctance to use the ICANN policy process?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></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><u><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#0563C1"><a href="mailto:jeff.neuman@comlaude.com">jeff.neuman@comlaude.com</a><o:p></o:p></span></u></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> David Conrad <david.conrad@icann.org> <br>
<b>Sent:</b> Monday, June 15, 2020 10:44 AM<br>
<b>To:</b> Jeff Neuman <jeff.neuman@comlaude.com><br>
<b>Cc:</b> Roy Arends <roy.arends@icann.org>; Dmitry Belyavsky <beldmit@gmail.com>; ncap-discuss@icann.org<br>
<b>Subject:</b> Re: [NCAP-Discuss] Top-level Domains for Private Internets IETF draft<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Jeff,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Roy has, as an individual and not in any way in relation to ICANN (other than he happens to work at ICANN), co-authored a proposal to document a convention of using the ISO-3166 “user defined” codes as private namespaces that are impossible
to ever collide with any names allocated by ICANN. His and Ed's Internet Draft documents the other technical uses of ISO-3166 codes. Since he is proposing the 2-letter codes identified by ISO-3166/MA (not ICANN) as “user defined” for a set of private name
spaces that are not exclusive of what the GNSO may or may not propose, it isn’t clear how this interacts with GNSO policy. Could you explain?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">-drc<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On Jun 15, 2020, at 6:40 AM, Jeff Neuman <<a href="mailto:jeff.neuman@comlaude.com">jeff.neuman@comlaude.com</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif">Roy,<br>
<br>
Why have you chosen to take this through the IETF track as opposed to taking it through the ICANN process. Seems to me that this is all about policy and very little about technical information in this Informational RFC.<br>
<br>
These are the very things that should be dealt with in the ICANN policy processes. The notion of creating namespaces for private use is purely policy and therefore dealing with this through the IETF, in my opinion, is not how we should be thinking about this.
Sure, it may be easier to get this type of thing through the IETF, but we should be more focused on improving the multi-stakeholder model to allow these types of discussions rather than trying to circumvent it.<br>
<br>
Has this been submitted to the GNSO?<br>
<br>
Jeff Neuman<br>
Senior Vice President<br>
Com Laude | Valideus<br>
D: +1.703.635.7514<br>
E:<span class="apple-converted-space"> </span></span><a href="mailto:jeff.neuman@comlaude.com"><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif">jeff.neuman@comlaude.com</span></a><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif"><br>
<br>
-----Original Message-----<br>
From: NCAP-Discuss <</span><a href="mailto:ncap-discuss-bounces@icann.org"><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif">ncap-discuss-bounces@icann.org</span></a><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif">> On Behalf Of
Roy Arends<br>
Sent: Friday, June 12, 2020 12:16 PM<br>
To: Dmitry Belyavsky <</span><a href="mailto:beldmit@gmail.com"><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif">beldmit@gmail.com</span></a><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif">><br>
Cc:<span class="apple-converted-space"> </span></span><a href="mailto:ncap-discuss@icann.org"><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif">ncap-discuss@icann.org</span></a><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif"><br>
Subject: Re: [NCAP-Discuss] Top-level Domains for Private Internets IETF draft<br>
<br>
I want to make a disclaimer here for complete transparency:<br>
<br>
I am the editor of that document. This draft is my individual submission and does not present an opinion, endorsement or anything like that from ICANN, ICANN affiliate (such as PTI) or the ICANN community.<br>
<br>
Warmly,<br>
<br>
Roy Arends<br>
ICANN staff member in the Office of the CTO.<br>
<br>
<br style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;text-align:start;-webkit-text-stroke-width: 0px;word-spacing:0px">
<br>
</span><o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif">On 12 Jun 2020, at 16:50, Dmitry Belyavsky <<a href="mailto:beldmit@gmail.com">beldmit@gmail.com</a>> wrote:<br>
<br>
Hello,<br>
<br>
I want to draw everybody's attention to the IETF draft "Top-level<br>
Domains for Private Internets"<br>
(<a href="https://datatracker.ietf.org/doc/draft-arends-private-use-tld/">https://datatracker.ietf.org/doc/draft-arends-private-use-tld/</a>)<br>
<br>
I think it should be taken to account in the group's upcoming analysis.<br>
<br>
--<br>
SY, Dmitry Belyavsky<br>
_______________________________________________<br>
NCAP-Discuss mailing list<br>
<a href="mailto:NCAP-Discuss@icann.org">NCAP-Discuss@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ncap-discuss">https://mm.icann.org/mailman/listinfo/ncap-discuss</a><br>
<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">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos">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.<o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal"><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif"><br>
________________________________<br>
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<br>
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="http://www.comlaude.com/"><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif">www.comlaude.com</span></a><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif"><</span><a href="https://comlaude.com/"><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif">https://comlaude.com</span></a><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif">><br>
_______________________________________________<br>
NCAP-Discuss mailing list<br>
</span><a href="mailto:NCAP-Discuss@icann.org"><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif">NCAP-Discuss@icann.org</span></a><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif"><br>
</span><a href="https://mm.icann.org/mailman/listinfo/ncap-discuss"><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif">https://mm.icann.org/mailman/listinfo/ncap-discuss</span></a><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif"><br>
<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 (</span><a href="https://www.icann.org/privacy/policy"><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif">https://www.icann.org/privacy/policy</span></a><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif">)
and the website Terms of Service (</span><a href="https://www.icann.org/privacy/tos"><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif">https://www.icann.org/privacy/tos</span></a><span style="font-size:8.5pt;font-family:"Menlo-Regular",serif">).
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><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<hr>
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
<a href="https://comlaude.com" target="_blank">www.comlaude.com</a>
</body>
</html>