ICANN/GNSO GNSO Email List Archives

[ga]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [ga] On Its Way: One of the Biggest Changes to the Internet

  • To: Danny Younger <dannyyounger@xxxxxxxxx>, "Prophet Partners Inc." <Domains@xxxxxxxxxxxxxxxxxxx>, ga@xxxxxxxxxxxxxx
  • Subject: Re: [ga] On Its Way: One of the Biggest Changes to the Internet
  • From: JFC Morfin <jefsey@xxxxxxxxxxxxxxxx>
  • Date: Thu, 11 Oct 2007 22:40:33 +0200


At 18:08 11/10/2007, Danny Younger wrote:
Ted raises an interesting point regarding usability.
My questions for the experts among us:

(1) Will e-mail work between an IDN domain and an
ASCII domain?
(2) If the current WHOIS system only accomodates
ASCII, will the WHOIS properly function in an IDN
environment?

Danny,
IDNs are a pure ICANN joke based on an IETF proposition named IDNA. The "A" stands for applications. This means that the IETF has created a left to right hierarchy within the DNS right to left hierarchy in creating a new zone separator, hence many new possible namespaces. One of these namespace is supposed to be IDNs for user applications supporting IDNA

Let me explain that in practical lay terms. Today domain names are made of labels separated by a ".", the top level being on the right end, the second level at the left of the top level, the third level at the left of the second level, and so on. The "." acts as a label external separator, connecting two labels. We all know that right to left hierarchy.

IETF has created the "--" internal separator to the label. This means that we now have the DN as "left_label_part--right_label_part.tld", you can also develop into "llp3--rlp3.llp2--rlp2.llp1--rlp1" for a 3rd level DN. By convention if llp2="xn" this is an IDN. There is absolutely no change to the DNS and DNS related tools.

The IDNA (application) is what is going to use "xn--y.z" formatted DNs in a special way. These applications have nothing specific to do with the Internet or the DNS. I can take the Firefox IDN Extension software, and even maybe the IE binary code and replace "xn" by "dy" to create the DYNA (Danny Younger's Naming Architecture). And you can start making a lot of money.

You may even create "dy--ny" as a DYccTLD for NY, ask Joe to put it on open roots and agree with NY ISP to support it, with a convention supported in the DYNA application for accepting "$" as the danycode equivalent for "dy--ny", and use the DYDN "$.$.$" the DNS will know as "dy--ny.dy--ny.dy--ny". You can even sell it to NY city?

Now, if you also make a deal with newNet, this can work everywhere tomorrow with their plugin which will translate your entry into "dy--ny.dy--ny.dy--ny.new.net". Works just fine with mails if the plug-in works, etc. And you may even have your $@$.$ mail address.

You have to remember that the DNS is NO part of the Internet (which is TCP/IP). It is an application running a service. And that in this DNS application ICANN is related to a very small portion of the DNS namespace which is the "IN" class. The reason why we do not use all the DNS possibility is purely because the M$ resolvers want it. The real boss is Bill Gates. The real problem is that there is no GPL Windows resolver. It would probably take one month to someone to develop and test it (Windows is nasty) and there would be ICANN and Registars no more.

This is why ICANN is not excited about IDNs. They could help people eventually understand. The DNS root is the biggest bluff of the century. Please understand the problem is not with the name space and the domain name concept. It is with the money that so many people want to make with it.
jfc







<<< Chronological Index >>>    <<< Thread Index >>>