Tina Dam answers: Are existing gTLDs going to be aliased to IDN extensions or not?

[Jay]

A little more info from Tina Dam on where ICANN are up to on aliasing:

http://idntraders.com/index.php?topic=90.msg261#msg261

[jacksonm]

Originally Posted by Rubber Duck

DNAME can only be used to alias an entire registry.

This is not really correct, remember that DNAME is only a resource record type and it can be used in many ways. It can be used to wholly redirect any branch of a namespace to any other domain. As a practical example, Verisign could do this in their own nameservers (if they had reserved idn.com for their own use):

.idn.com.  DNAME    .xn-xyz.

Now, all name lookups for the idn.com namespace would actually be referred to the .xn-xyz namespace for answers. So you see, they could alias a domain itself to a new extension. Not sure how useful this would be, but this does serve as a good practical example of what DNAME really does.

Now, here is an example of how you would use DNAME resource records to do extension aliasing (aliasing 5 IDN equivalents for dot com to .com itself):

.xn--xyza.  DNAME    .com.
.xn--xyzb.  DNAME    .com.
.xn--xyzc.  DNAME    .com.
.xn--xyzd.  DNAME    .com.
.xn--xyze.  DNAME    .com.

Originally Posted by Rubber Duck

It cannot be used to do them all on a case by case basis according to whether the registrant has stumped up or not. If it were done in the root, then all aliased extensions would be aliased for all registrants for each extension. There would be no scope to gather subscriptions except from a global increase in the registry fee. Perhaps that would happen, but the chances are that the ASCII mob would be asked to stump up as well!

This is correct.


.

[Rubber Duck]

Yes, I went to great length at one time to try to point out Vint Cerf that DNAME could be used by the Chinese to great an unlimited number of TLDs under the dot CN so that it the dot CN did not have to be specifically used on second level names, such as .com.cn. Perhaps I shouldn't have said anything.

[blastfromthepast]

Originally Posted by touchring

4) Verisign takes .ком.

So, all attention should be on Verisign.

So far, what we have going for Verisign, based on past performance:

1) Launched IDN.com TEST registrations in 2000.

2) Rolled over TEST registrations to real registrations when Punycode standard came out.
=> Early "test" registrants benefited, much to the annoyance of those who thought it was "just a test."

3) Produced aliasing proposal for ICANN shows support of aliasing idea for .com.

4) Have been keeping quiet.

NEXT STEP) Rolled over .com registrants to .ком, once approved for .ком, which they will be.
=> This is what we need to focus on.

[bwhhisc]

Originally Posted by blastfromthepast

So, all attention should be on Verisign.

So far, what we have going for Verisign, based on past performance:
1) Launched IDN.com TEST registrations in 2000.
2) Rolled over TEST registrations to real registrations when Punycode standard came out.
=> Early "test" registrants benefited, much to the annoyance of those who thought it was "just a test."
3) Produced aliasing proposal for ICANN shows support of aliasing idea for .com.
4) Have been keeping quiet.
NEXT STEP) Rolled over .com registrants to .ком, once approved for .ком, which they will be.
=> This is what we need to focus on.

Worth the effort. Seems that from the ICANN blog conversation and comments by Tina Dam when Verisign is
ready they are free to make this request to ICANN when they wish.

[Alphamale]

Originally Posted by bwhhisc

Worth the effort. Seems that from the ICANN blog conversation and comments by Tina Dam when Verisign is
ready they are free to make this request to ICANN when they wish.

not according to verysigh this is an ICANN matter see the other thread

[bwhhisc]

Originally Posted by Alphamale

not according to verysigh this is an ICANN matter see the other thread

This no doubt will fall into that area of policy known as "Catch 22".