<div dir="ltr"><div>Milton, I'm glad to see there's now been lots of responses to Ted Cruz's spin and hopefully this debunking will hit Trump's peddling as well. They probably won't learn to stop peddling lies but at least they've underestimated some knowledgeable people within ICANN, who are able to describe the IANA transition in layman's terms. <br><br>I learned a couple of things from that article, too.. =)<br><br></div>-Raoul<br></div><div class="gmail_extra"><br><div class="gmail_quote">On 22 September 2016 at 18:37, Martin Boyle <span dir="ltr"><<a href="mailto:Martin.Boyle@nominet.uk" target="_blank">Martin.Boyle@nominet.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Sorry for the delay, Nigel.<br>
<br>
I agree with your conclusion.<br>
<br>
As you note, the .int TLD is quite well identified other than for the international databases: there is no ambiguity in scope for organizations established by international treaties.<br>
<br>
If I have understood correctly, international databases were transferred to be included under .arpa some long time ago.<br>
<br>
Either way, I see no reason why .int should be opened up beyond organizations established by international treaty at this stage and certainly not without a properly constituted policy development process (which would need to establish a process for appointing a new operator).<br>
<br>
None of this, of course, nullifies your conclusion!<br>
<span class="HOEnZb"><font color="#888888"><br>
Martin<br>
</font></span><span class="im HOEnZb"><br>
<br>
-----Original Message-----<br>
From: Nigel Roberts [mailto:<a href="mailto:nigel@channelisles.net">nigel@channelisles.net</a><wbr>]<br>
Sent: 16 September 2016 12:05<br>
To: Martin Boyle <<a href="mailto:Martin.Boyle@nominet.uk">Martin.Boyle@nominet.uk</a>><br>
Cc: Christopher Wilkinson <<a href="mailto:lists@christopherwilkinson.eu">lists@christopherwilkinson.eu</a><wbr>>; <a href="mailto:accountability-cross-community@icann.org">accountability-cross-<wbr>community@icann.org</a><br>
Subject: Re: [CCWG-ACCT] Answers to some common questions being encountered by the ICANN staff<br>
<br>
</span><div class="HOEnZb"><div class="h5">The only reference is descriptive rather than policy setting. .INT predates RFC1591.<br>
<br>
It says, simply "This domain is for organizations established by international treaties, or international databases". (The latter term is undefined, but includes telephony applications).<br>
<br>
You will find this text alongside all the other (at the time) existing generic domains as follows.<br>
<br>
Much of what is written below has been changed, and much of what has been changed was changed outside ICANN.<br>
<br>
I would be interested to know which policy decision classified some of the gTLDs in this list as "dehors ICANN", and which within.<br>
<br>
But as two of the gTLDs described in RFC 1591 are currently extremely sensitive (MIL and GOV),from what I heard in the Senate hearing, perhaps its best not to ask for an answer to this until after the end of the month??<br>
<br>
<br>
<br>
<br>
> World Wide Generic Domains:<br>
><br>
> COM - This domain is intended for commercial entities, that is<br>
> companies. This domain has grown very large and there is<br>
> concern about the administrative load and system performance if<br>
> the current growth pattern is continued. Consideration is<br>
> being taken to subdivide the COM domain and only allow future<br>
> commercial registrations in the subdomains.<br>
><br>
> EDU - This domain was originally intended for all educational<br>
> institutions. Many Universities, colleges, schools,<br>
> educational service organizations, and educational consortia<br>
> have registered here. More recently a decision has been taken<br>
> to limit further registrations to 4 year colleges and<br>
> universities. Schools and 2-year colleges will be registered<br>
> in the country domains (see US Domain, especially K12 and CC,<br>
> below).1<br>
><br>
> NET - This domain is intended to hold only the computers of network<br>
> providers, that is the NIC and NOC computers, the<br>
> administrative computers, and the network node computers. The<br>
> customers of the network provider would have domain names of<br>
> their own (not in the NET TLD).<br>
><br>
> ORG - This domain is intended as the miscellaneous TLD for<br>
> organizations that didn't fit anywhere else. Some non-<br>
> government organizations may fit here.<br>
><br>
> INT - This domain is for organizations established by international<br>
> treaties, or international databases.<br>
><br>
> United States Only Generic Domains:<br>
><br>
> GOV - This domain was originally intended for any kind of government<br>
> office or agency. More recently a decision was taken to<br>
> register only agencies of the US Federal government in this<br>
> domain. State and local agencies are registered in the<br>
> country<br>
><br>
><br>
><br>
> Postel [Page 2]<br>
><br>
<br>
> RFC 1591 Domain Name System Structure and Delegation March 1994<br>
><br>
><br>
> domains (see US Domain, below).<br>
><br>
> MIL - This domain is used by the US military.<br>
<br>
______________________________<wbr>_________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-<wbr>Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/accountability-cross-<wbr>community</a><br>
</div></div></blockquote></div><br></div>