Where is the DNS moving and is ICANN right?
Risking being in the minority, I would like to express my opinion on the recent decisions of ICANN in the context of the development of the domain system as a whole.
What we have had for many years and have to this day.
1. Strictly restricted sign for use in domain names - roughly speaking, 26 Latin uppercase letters, 10 Arabic numerals and a hyphen. Latin (askishnaya) point is used as a separator nodes of the hierarchy. All other alphabets of the world are not represented, that is, they are discriminated. Let me remind you that the Unicode standard was published sixteen years ago .
')
2. A strictly limited set of top-level domains (TLDs) - two-letter geographic plus a handful of historical com-net-org, .mil exclusively for the US military, .nato for it internationally, .edu for (American!) Educational institutions. All other countries must be established under their geographical domain, that is, they are discriminated. At the beginning of the century a handful was added, such as .info, .mobi, .travel, and similarly, for supposedly specialized services. All of them, one hundred percent, are formed from English transcription, and some are also from distorted, like .biz. Other languages ​​are not represented once, that is, they are discriminated.
3. Thanks to the driving force of progress, that is, the bubble, a purely squatted domain .eu was created, which broke the last order of the order in this system, that is, the reservation of two-letter domains only for countries and for nothing else. Two-letter domains somehow met the ISO 3166 standard, and now it has been lost. If a newly emerged country receives an EU code, it will not be able to get its domain because it is busy. Comments are not needed.
4. Due to the artificial restriction on top-level domains, some domains of some countries became much more popular than others, due to completely arbitrary and random reasons , like the harmoniousness of an ISO code in the desired language (cc, to, nu, cx, fm, tv, md and so on), or free registration (tk). I already wrote here about this phenomenon, look for Tokelau.
5. Due to the desire of localization, companies are forced to register a new domain in each country where they conduct business (google.com, google.fr, google.it, and so on 82 times). Pretty often there is a conflict with the already registered legitimate domains in these countries. This leads to many years of tedious litigation and confusion for users. Squatters are crawling. In the same example: gmail.de could not be sued, gmail.pl was occupied for a very long time: Grupa Młodych Artystów i Literatów existed long before Google’s postal service.
6. Approval of wild and absurd applications for TLDs, like .cat and .bzh for propaganda of Catalan and Breton languages, respectively. Have you heard of these? Dieub ha par en o dellezegezh hag o gwirioĂą eo ganet an holl dud. But the matter is progressive (see above), because applications are supported by six-digit tranches. How many of you believe that the sonorous domain .cat is really used for the prosperity of the culture of the surroundings of the glorious city of Barcelona?
7. Forced disappearance from the network of domains whose TLD has ceased to exist for reasons independent of them. This refers to the states that have died in the Bose, and the names that have been brought up in the .cz, .su, and .yu zones. My country can cease to exist, or so it is called, or I can move, and the TLD begins to be a false entity that has been imposed on me, and can bring down my essence.
8. The actual dilution of the existing two-tier system into a flat one: the .com TLD means practically nothing in our time, it does not communicate either the attitude towards commerce or the United States. This is well illustrated by the behavior of many browsers, which, when you enter a single word in the address string, by default try to attach behind the ".com".
1. Allow the use of any Unicode characters in the names, with the following restrictions.
you can use only alphanumeric characters (of any alphabet and any numbers);
within the name, it is possible to use symbols of one, and only one alphabet, to exclude the variants “Microsoft” with the Cyrillic “o” or “c”. By alphabet we mean “script” in unicode.
punctuation is prohibited so that there is no temptation to use something like a dot to be misleading.
It is necessary to keep the existing system of reduction to one register, in those alphabets where the register is different. It is unlikely that anyone would distinguish between .gibd and i.HIBDD.
2. Allow the registration of any top-level domains. What ICANN has now done is a progressive step (test word: loot), in the sense of potential superprofits of the registrars and the office itself, but the tendency, nevertheless, must be relied upon to be correct. It will take several years, and the said six-figure TLD contributions will be four and three digits, and over time and unequivocal, like .com, this is an inevitable process. The temptation to register .mycompany and get ahead of all possible Mycompany Ltd, Mycompany GmbH, Mycompany OY, Mycompany szoo in any countries will be too great.
Technical no: a small extension of the DNS protocol. Logistic, too, because this system does not cancel the previous one, but complements it. As for the inconvenience of non-Latin (Russian, Chinese, etc.) domains, there is one simple consideration - the market. If it is convenient, companies will register. And if customers find it inconvenient, they will not, that's all. No one forces you to move from an existing .com or .ru. The only problem, the solution of which I do not see, is a question of ownership in relation to the top-level domain. Perhaps, dear readers will share their thoughts on this issue.
UPD I : special thanks for the collapse of karma after this, and after all my recent articles. I know that an independent position is not honored.
UPD II : A hot discussion has begun on whether it is good to have domains in Unicode or not. I remind you that domains in unicode (“international”) have been resolved in many registries for many years by hacking through the unicode reduction of unicode (“pyunicode”), and thousands of Chinese, Russian, Arab, Swedish and other domains of the SECOND level have long been registered.
All I suggested was to show consistency, and to allow the same at the FIRST level, that is, the TLD. The details of the implementation (leave as is, that is, pyunicode, or bring everything to UTF-8 encoding) are not so important.
UPD III : Added items 7 and 8.
Problem
What we have had for many years and have to this day.
1. Strictly restricted sign for use in domain names - roughly speaking, 26 Latin uppercase letters, 10 Arabic numerals and a hyphen. Latin (askishnaya) point is used as a separator nodes of the hierarchy. All other alphabets of the world are not represented, that is, they are discriminated. Let me remind you that the Unicode standard was published sixteen years ago .
')
2. A strictly limited set of top-level domains (TLDs) - two-letter geographic plus a handful of historical com-net-org, .mil exclusively for the US military, .nato for it internationally, .edu for (American!) Educational institutions. All other countries must be established under their geographical domain, that is, they are discriminated. At the beginning of the century a handful was added, such as .info, .mobi, .travel, and similarly, for supposedly specialized services. All of them, one hundred percent, are formed from English transcription, and some are also from distorted, like .biz. Other languages ​​are not represented once, that is, they are discriminated.
3. Thanks to the driving force of progress, that is, the bubble, a purely squatted domain .eu was created, which broke the last order of the order in this system, that is, the reservation of two-letter domains only for countries and for nothing else. Two-letter domains somehow met the ISO 3166 standard, and now it has been lost. If a newly emerged country receives an EU code, it will not be able to get its domain because it is busy. Comments are not needed.
4. Due to the artificial restriction on top-level domains, some domains of some countries became much more popular than others, due to completely arbitrary and random reasons , like the harmoniousness of an ISO code in the desired language (cc, to, nu, cx, fm, tv, md and so on), or free registration (tk). I already wrote here about this phenomenon, look for Tokelau.
5. Due to the desire of localization, companies are forced to register a new domain in each country where they conduct business (google.com, google.fr, google.it, and so on 82 times). Pretty often there is a conflict with the already registered legitimate domains in these countries. This leads to many years of tedious litigation and confusion for users. Squatters are crawling. In the same example: gmail.de could not be sued, gmail.pl was occupied for a very long time: Grupa Młodych Artystów i Literatów existed long before Google’s postal service.
6. Approval of wild and absurd applications for TLDs, like .cat and .bzh for propaganda of Catalan and Breton languages, respectively. Have you heard of these? Dieub ha par en o dellezegezh hag o gwirioĂą eo ganet an holl dud. But the matter is progressive (see above), because applications are supported by six-digit tranches. How many of you believe that the sonorous domain .cat is really used for the prosperity of the culture of the surroundings of the glorious city of Barcelona?
7. Forced disappearance from the network of domains whose TLD has ceased to exist for reasons independent of them. This refers to the states that have died in the Bose, and the names that have been brought up in the .cz, .su, and .yu zones. My country can cease to exist, or so it is called, or I can move, and the TLD begins to be a false entity that has been imposed on me, and can bring down my essence.
8. The actual dilution of the existing two-tier system into a flat one: the .com TLD means practically nothing in our time, it does not communicate either the attitude towards commerce or the United States. This is well illustrated by the behavior of many browsers, which, when you enter a single word in the address string, by default try to attach behind the ".com".
Decision
1. Allow the use of any Unicode characters in the names, with the following restrictions.
you can use only alphanumeric characters (of any alphabet and any numbers);
within the name, it is possible to use symbols of one, and only one alphabet, to exclude the variants “Microsoft” with the Cyrillic “o” or “c”. By alphabet we mean “script” in unicode.
punctuation is prohibited so that there is no temptation to use something like a dot to be misleading.
It is necessary to keep the existing system of reduction to one register, in those alphabets where the register is different. It is unlikely that anyone would distinguish between .gibd and i.HIBDD.
2. Allow the registration of any top-level domains. What ICANN has now done is a progressive step (test word: loot), in the sense of potential superprofits of the registrars and the office itself, but the tendency, nevertheless, must be relied upon to be correct. It will take several years, and the said six-figure TLD contributions will be four and three digits, and over time and unequivocal, like .com, this is an inevitable process. The temptation to register .mycompany and get ahead of all possible Mycompany Ltd, Mycompany GmbH, Mycompany OY, Mycompany szoo in any countries will be too great.
Difficulties
Technical no: a small extension of the DNS protocol. Logistic, too, because this system does not cancel the previous one, but complements it. As for the inconvenience of non-Latin (Russian, Chinese, etc.) domains, there is one simple consideration - the market. If it is convenient, companies will register. And if customers find it inconvenient, they will not, that's all. No one forces you to move from an existing .com or .ru. The only problem, the solution of which I do not see, is a question of ownership in relation to the top-level domain. Perhaps, dear readers will share their thoughts on this issue.
UPD I : special thanks for the collapse of karma after this, and after all my recent articles. I know that an independent position is not honored.
UPD II : A hot discussion has begun on whether it is good to have domains in Unicode or not. I remind you that domains in unicode (“international”) have been resolved in many registries for many years by hacking through the unicode reduction of unicode (“pyunicode”), and thousands of Chinese, Russian, Arab, Swedish and other domains of the SECOND level have long been registered.
All I suggested was to show consistency, and to allow the same at the FIRST level, that is, the TLD. The details of the implementation (leave as is, that is, pyunicode, or bring everything to UTF-8 encoding) are not so important.
UPD III : Added items 7 and 8.
Source: https://habr.com/ru/post/28948/
All Articles