Public Comment

Public Comment is a vital part of our multistakeholder model. It provides a mechanism for stakeholders to have their opinions and recommendations formally and publicly documented. It is an opportunity for the ICANN community to effect change and improve policies and operations.

Submissions for this Proceeding

Proposed Top-Level Domain String for Private Use

Search Public Comment Submissions For This Proceeding

To search for keywords within Public Comment submissions documents or pages, type in the keyword and press Enter after each selection.

Proposed Top-Level Domain String for Private Use Submission - I Love Domains - United States o' America
23 February 2024

Submission Summary:

I Love Domains – United States o’ America, the operator of the .UnitedStatesoAmerica.com extension, has come forward to provide a contribution to the construction of a fair and diverse internet with ICANN.

 

For any questions, please send an email to:

Davies-lewis@ilovedomains.UnitedStatesoAmerica.com

 

I advise that the delegation of strings for private use be strictly observed and treated, as by provid...


Proposed Top-Level Domain String for Private Use Submission - Google
21 February 2024

Submission Summary:

Google endorses the use of ".internal" as a private use and reserved TLD. The string meets the primary criteria for such an internal use name and is already in use for this purpose among a number of organizations.


Proposed Top-Level Domain String for Private Use Submission - The IO Foundation
15 February 2024

Submission Summary:

The IO Foundation does not believe that .internal should ever be considered under different scripts than Latin.


Proposed Top-Level Domain String for Private Use Submission - Security and Stability Advisory Committee (SSAC)
08 February 2024

Submission Summary:


SSAC2024-01 is a public comment issued by the ICANN Security and Stability Advisory Committee (SSAC) supporting the IANA's determination to reserve ".INTERNAL" for private use as outlined in SAC113: the SSAC Advisory on Private-Use TLDs. The SSAC confirms that the reservation of ".INTERNAL" meets the selection criteria specified in Section 4.1 of SAC113. The document further references Appendix A of SAC113, which provides additional...


Proposed Top-Level Domain String for Private Use Submission - Adams, John
08 February 2024

Submission Summary:

Multiple TLDs are needed to support private networks of various sizes. Please include ".lan" (local area network) and ".wan" (wide area network) in addition to ".internal" as reserved TLDs for private networks. This will provide flexibility when designing private networks and eliminate name conflicts with potential future public domain names.


Proposed Top-Level Domain String for Private Use Submission Retracted - McGuckin, Todd
07 February 2024
This Submission has been removed.

Proposed Top-Level Domain String for Private Use Submission - Martinez, Federico
04 February 2024

Submission Summary:

I support the idea of having at least one reserved TLD for internal use, specially for usage with IPv6 addresses since they are harder to memorize.


I also agree with others that .internal is long and that having another option such as .lan would be ideal.


Proposed Top-Level Domain String for Private Use Submission - R, B
04 February 2024

Submission Summary:

What strikes me most is that, to this day, the reserved, non-routable IP address ranges were associated with unresolvable .local domains.

The logic was coherent.


With your proposal, you want to provide a *public* resolution of non-routable IP addresses: this means first and foremost a leak…

An attacker wishing to enumerate targets on a non-routable network will then be able to listen to DNS traffic to gather inform...


Proposed Top-Level Domain String for Private Use Submission - Kumari, Warren
01 February 2024

Submission Summary:

[ Speaking as an individual only.]


As the author of a draft in the IETF which originally proposed this (https://datatracker.ietf.org/doc/pdf/draft-wkumari-dnsop-internal-00), and one of the primary authors of ICANN SSAC113, I fully support the IANA's proposed string.



In addition to meeting the criteria in SAC113 (as demonstrated by .internal being used in the examples) .internal is currently the hig...


Proposed Top-Level Domain String for Private Use Submission - Hart, Matthew
01 February 2024

Submission Summary:

.lan, .local, and .internal would all be appropriate options.

The benefit of .internal is that it is much less likely to be already currently deployed across internal network services currently. .local can be seen at the local domain level quite frequently. With that in mind, .lan is much shorter and still well understood by most.

It was mentioned in the proposal that .internal carries the implication that it is never accessible t...


Proposed Top-Level Domain String for Private Use Submission - Simpson, Colin
01 February 2024

Submission Summary:

An excellent suggestion to reserve a private top-level domain.

".internal" is a bit long, is a minor comment.

I don't see why you don't just reserve the sensible top 5 or 10 currently used internal TLD (which isn't a large number).

You might as well as people will probably keep using these anyway, so it's not like they can be assigned easily.

i.e. home, lan, dhcp, corp, internal, localdomain, intra


Proposed Top-Level Domain String for Private Use Submission - Moravec, Pavel
01 February 2024

Submission Summary:

The internal root domain seems to be unsuitable due to its length - if needed to be typed manually - and (already in document) mentioned confusion with .int by users. Why was a TLD SELF, i.e. .self. not considered, as it seems to be unallocated and not a part of even unofficially used root domains (unlike the .here. domain which would have been even better, but is already allocated)?


Proposed Top-Level Domain String for Private Use Submission Retracted - Roig, Jon
01 February 2024
This Submission has been removed.

Proposed Top-Level Domain String for Private Use Submission - Eggebroten, Tim
31 January 2024

Submission Summary:

please also reserve .lan or some other three letter TLD for private use.


Proposed Top-Level Domain String for Private Use Submission - Smith, Laura
31 January 2024

Submission Summary:

What about .corp, .home, .mail which ICANN have effectively banned anyway ? Why not just formalise them ?


Proposed Top-Level Domain String for Private Use Submission - Glanville, Alex
31 January 2024

Submission Summary:

There is already a .local domain set up by the IETF for accessing devices on a local area network. Has the .local domain been considered and, if so, why is .internal a stronger candidate? How would .local and .internal work together?


Proposed Top-Level Domain String for Private Use Submission - OTTE, Denis
31 January 2024

Submission Summary:

Positive aspects:

+ Very good proposal to have a TLD dedicated for private use!

+ Good points on why to prefer .internal instead of .private. No arguments there.


Negative aspects:

- .INTERNAL might be a bit long compared to .private (+1 char), but still acceptable.


Other thoughts:

- Why not also having a shorter, 3-char TLD to serve the same purpose? I guess (just my opinion - I did not...


Proposed Top-Level Domain String for Private Use Submission - Humphreys, George
31 January 2024

Submission Summary:

Support proposal as-is

* internal conveys purpose to layman and tech-literate

* private use TLD allows for better support and user-friendliness for home networking (no ambiguity on 192.168.0.1 or 192.168.1.1 etc)

* domains are more widely shared and see vs IPs

* IPv6 addresses may be used and greatly benefit from a TLD

* .internal should not be routed to a public (Internet) resource and should be managed by the i...


Proposed Top-Level Domain String for Private Use Submission - Humpert, Ben
30 January 2024

Submission Summary:

I suggest to use .lan instead of .internal or .private.


.lan is much faster and easier to type, especially on mobile devices (including numeric keypads, eg. 555266)


.lan shares the same "security risks" with .internal or .private but because it is much shorter, the risk is lower, i.e. using a capital "i" or Cyrillic letters.


.lan is the abbreviation of "Local Area Network" so it would make per...


Proposed Top-Level Domain String for Private Use Submission - Lehman, Luke
27 January 2024

Submission Summary:

Having private tld's I think are long overdue. There hasn't been clear guidance on what to specifically use when setting up your own private domain. I think using only .internal as the sole English language private tld may provide option


The IETF has a draft RFC that suggests additional tld that should be reserved due to the tld "has been queried and a root name server has responded to the query with a non-existent domain (NXD...