Private Use TLD: Difference between revisions
Created page with "A '''Private Use TLD''' is a DNS label that cannot correspond to any current or future delegation in the global DNS root. This reserved label would serve as a top-level do..." |
m added Category:TLD using HotCat |
||
Line 1: | Line 1: | ||
A '''Private Use TLD''' is a [[DNS]] label that cannot correspond to any current or future delegation in the global DNS root. This reserved label would serve as a top-level domain (TLD) for a privately resolvable namespace with the goals of preventing collisions with globally delegated names, increasing predictability, and decreasing erroneous queries to root servers. The reason behind the recommendation for a private use TLD is that the ad hoc usage of TLDs for private purposes is currently uncoordinated and can harm Internet users. In SAC113, the [[SSAC]] recommended that the [[ICANN Board]] ensure a string reserved at the top level for private use and that it never be delegated. The SSAC proposed the following criteria for selecting the reserved string: It must be a valid DNS label, should not already be delegated in the root zone, should not be confusingly similar to existing TLDs, and should be relatively short, memorable, and meaningful.<ref>[https://www.icann.org/en/system/files/files/sac-113-en.pdf SAC113, ICANN Files]</ref> | A '''Private Use TLD''' is a [[DNS]] label that cannot correspond to any current or future delegation in the global DNS root. This reserved label would serve as a top-level domain (TLD) for a privately resolvable namespace with the goals of preventing collisions with globally delegated names, increasing predictability, and decreasing erroneous queries to root servers. The reason behind the recommendation for a private use TLD is that the ad hoc usage of TLDs for private purposes is currently uncoordinated and can harm Internet users. In SAC113, the [[SSAC]] recommended that the [[ICANN Board]] ensure a string reserved at the top level for private use and that it never be delegated. The SSAC proposed the following criteria for selecting the reserved string: It must be a valid DNS label, should not already be delegated in the root zone, should not be confusingly similar to existing TLDs, and should be relatively short, memorable, and meaningful.<ref>[https://www.icann.org/en/system/files/files/sac-113-en.pdf SAC113, ICANN Files]</ref> | ||
==History== | |||
In September 2020, SSAC published SAC113. In March 2023, ICANN Org published a summary report on [[Public Comment]]s received on the topic of private use TLDs. The comments concerned: | |||
* The need for direct comment on the candidate string itself and the ability to re-evaluate selection criteria | |||
* Subjective assessments should not be made by [[IANA]] | |||
* Add evaluation criteria for confusing similarity, memorability, and meaningfulness; for potential conflicts with future TLDs | |||
* Perform a trademark search | |||
* Greater specificity is needed for the staff selection process | |||
* Timely implementation | |||
* Show why it's necessary | |||
* Requests for specific candidate strings | |||
In the report, ICANN Org stated that the [[IANA]] department is appropriate for implementing the procedure. The org noted practical concerns over conflicts with potential future TLDs and conducting comprehensive trademark searches. The Org planned to provide specificity on the staff selection process and used SSAC's SAC113 recommendations as justification.<ref>[https://itp.cdn.icann.org/en/files/root-system/public-comment-summary-report-proposed-procedure-selecting-top-level-domain-string-private-use-27-03-2023-en.pdf SAC113 Public Comment Report, ICANN Files]</ref> | |||
==References== | ==References== | ||
[[Category:TLD]] |
Latest revision as of 16:08, 18 May 2023
A Private Use TLD is a DNS label that cannot correspond to any current or future delegation in the global DNS root. This reserved label would serve as a top-level domain (TLD) for a privately resolvable namespace with the goals of preventing collisions with globally delegated names, increasing predictability, and decreasing erroneous queries to root servers. The reason behind the recommendation for a private use TLD is that the ad hoc usage of TLDs for private purposes is currently uncoordinated and can harm Internet users. In SAC113, the SSAC recommended that the ICANN Board ensure a string reserved at the top level for private use and that it never be delegated. The SSAC proposed the following criteria for selecting the reserved string: It must be a valid DNS label, should not already be delegated in the root zone, should not be confusingly similar to existing TLDs, and should be relatively short, memorable, and meaningful.[1]
History[edit | edit source]
In September 2020, SSAC published SAC113. In March 2023, ICANN Org published a summary report on Public Comments received on the topic of private use TLDs. The comments concerned:
- The need for direct comment on the candidate string itself and the ability to re-evaluate selection criteria
- Subjective assessments should not be made by IANA
- Add evaluation criteria for confusing similarity, memorability, and meaningfulness; for potential conflicts with future TLDs
- Perform a trademark search
- Greater specificity is needed for the staff selection process
- Timely implementation
- Show why it's necessary
- Requests for specific candidate strings
In the report, ICANN Org stated that the IANA department is appropriate for implementing the procedure. The org noted practical concerns over conflicts with potential future TLDs and conducting comprehensive trademark searches. The Org planned to provide specificity on the staff selection process and used SSAC's SAC113 recommendations as justification.[2]