Good news for Russian IDN.com holders.

[Explorer]

http://webnames.ru/scripts/newsmaker.pl?news_id=14

IDN.RU might not happen at all and they will get the ball rolling with .РФ (Russian Federation) instead.

There is no doubt that IDN.RU would have been the king in Russia, followed by IDN.com and IDN.РФ. Now, without IDN.RU and unknown to Russians IDN.РФ (which is still probably several years away), IDN.com should rule the Russian IDN domain market.

[Alphamale]

Good find.

so IDN.РФ is a seperate name space - no mention of mapping to anything.

[Explorer]

Originally Posted by Alphamale

so IDN.РФ is a seperate name space - no mention of mapping to anything.

That's right. They will simply follow ICANN's procedure and timeline with respect to IDN.IDN.

[Rubber Duck]

Originally Posted by Explorer

That's right. They will simply follow ICANN's procedure and timeline with respect to IDN.IDN.

Is this actually going to resolve through the ICANN DNS, or are we talking another obscure Internet Channel here?

[Explorer]

Originally Posted by Rubber Duck

Is this actually going to resolve through the ICANN DNS, or are we talking another obscure Internet Channel here?

This is all ICANN-comliant.

[Rubber Duck]

This has to be nonsense.

The Russians can put what they like under dot RU.

They will also undoubtedly get an iccTLD, but nobody for the moment can say what it is. ICANN policy is not yet sufficiently developed for that to happen.

The links give by Drewbert yesterdays suggest Russia would be written out in full in the extension in Cyrillic. Whilst, that seems a bit bizarre to me it tends to suggest nothing is happening. At least nothing straight and above board.

Further to previous:

http://icann.org/meetings/lisbon/tra...rs-27mar07.htm

>>WOLFGANG KLEINWAECHTER: My name is Wolfgang Kleinwachter. I'm from the University of Aarhus, and I have a question to IDN.IDN. It's more a policy question. You know, formerly, the dot IDN would be a new TLD, a new root zone file, so -- and my question is also to ICANN. Do they have a policy? Will this be a new delegation, or is this part of the delegation for dot GR in -- in Roman letters or could it include also the opportunity to create another national registry, and has it to be the same letters as the characters, like GR? I heard from Russian colleagues that they have dot RU in Latin letters and they plan to have a dot RF for Russian Federation in Cyrillic letters, which would [inaudible] dot RU, but it means the question is, is this now a start -- do we start a process of multiplying national registries or will this be under -- in the hand of the existing, because at the moment, you know, the ccTLD is a monopoly in the country, so would this mean that you have then suddenly competition on the ccT level in the country between dot GR and dot IDN? Thank you.

[Explorer]

Originally Posted by Rubber Duck

This has to be nonsense.

The Russians can put what they like under dot RU.

They will also undoubtedly get an iccTLD, but nobody for the moment can say what it is. ICANN policy is not yet sufficiently developed for that to happen.

The links give by Drewbert yesterdays suggest Russia would be written out in full in the extension in Cyrillic. Whilst, that seems a bit bizarre to me it tends to suggest nothing is happening. At least nothing straight and above board.

Further to previous:

http://icann.org/meetings/lisbon/tra...rs-27mar07.htm

>>WOLFGANG KLEINWAECHTER: My name is Wolfgang Kleinwachter. I'm from the University of Aarhus, and I have a question to IDN.IDN. It's more a policy question. You know, formerly, the dot IDN would be a new TLD, a new root zone file, so -- and my question is also to ICANN. Do they have a policy? Will this be a new delegation, or is this part of the delegation for dot GR in -- in Roman letters or could it include also the opportunity to create another national registry, and has it to be the same letters as the characters, like GR? I heard from Russian colleagues that they have dot RU in Latin letters and they plan to have a dot RF for Russian Federation in Cyrillic letters, which would [inaudible] dot RU, but it means the question is, is this now a start -- do we start a process of multiplying national registries or will this be under -- in the hand of the existing, because at the moment, you know, the ccTLD is a monopoly in the country, so would this mean that you have then suddenly competition on the ccT level in the country between dot GR and dot IDN? Thank you.

All the Russians are saying is they would like their .IDN extention to be .РФ as per ICANN's IDN.IDN solution. Plus, they are saying they won't have IDN.RU, which makes sense.

All I am saying is that .РФ will not be able to compete with IDN.com. Plus, I think when .РФ opens, IDN.com owners will get first priority in getting those IDN.РФ names.

[Rubber Duck]

Originally Posted by Explorer

All the Russians are saying is they would like their .IDN extention to be .РФ as per ICANN's IDN.IDN solution. Plus, they are saying they won't have IDN.RU, which makes sense.

All I am saying is that .РФ will not be able to compete with IDN.com. Plus, I think when .РФ opens, IDN.com owners will get first priority in getting those IDN.РФ names.

Having listened to the Workshop this afternoon on the Webcast it is clear that ICANN has no idea where this is going.

What is clear is that ccTLD will not be able to be introduced in advance of IDN.gTLD.

It is looking increasingly likely that IDN.ccTLD will require DNAMES for its full implementation as the user requirement Matrix seems to be going multi-dimensional.

Having said that, it means that a few special cases are likely to get fast-tracked as Test-Bed or Experimental.

Those that have been worry about the implications of NS on dot Com, were clearly not even asking the right questions, let alone coming up with sensible answers.

If the guys that attend Traffics were attending these meeting they would have to download a completely new set of Drivers for installed processing equipment to fuction at all!

[blastfromthepast]

Thank you for posting that, I'm out to celebrate.

[bwhhisc]

Originally Posted by blastfromthepast

Thank you for posting that, I'm out to celebrate.

Yup, good news coming from all ports of call today...Japan, Russia, and (indirectly) Greece.
Really liked the read about the application of DNAME to resolve the Greek linguisical accent challenges.
A few more strong cases about the practicality of DNAME mapping would be very timely right now.

[yanni]

Originally Posted by bwhhisc

Really liked the read about the application of DNAME to resolve the Greek linguisical accent challenges.

Well, besides the .gr where everything works fine, it will be a nightmare for .com and .net as there are versions of the same domain registered by different people.

Who gets what?

[blastfromthepast]

Originally Posted by yanni

Well, besides the .gr where everything works fine, it will be a nightmare for .com and .net as there are versions of the same domain registered by different people.

Who gets what?

Well, simple. If you want to own it all, you buy out the other holders.

[yanni]

Technically, the person who owns the un-accented version gets the accented one since he/she already owns the correct capitalization of the word.

It will be interesting to watch as it unfolds.

[Rubber Duck]

Originally Posted by bwhhisc

Yup, good news coming from all ports of call today...Japan, Russia, and (indirectly) Greece.
Really liked the read about the application of DNAME to resolve the Greek linguisical accent challenges.
A few more strong cases about the practicality of DNAME mapping would be very timely right now.

Not out yet but you seriously need to get hold of Transcript of IDN - GAC - GNSO & ccNSO Working Groups Workshop. The idea that ccTLD is going to be suited ultimately to an NS solution is dead in the water. Everyone is calling for implementation of what is "ready to go".

The full implementation of ccTLD has been effectively kicked into the long grass along with DNAME. It looks as though a small selection of ccTLD AND gTLD will be implemented as NS, in the very near future. This could be even better than DNAME, because it means that Chinese, Japanese and Russian at least could be implemented very soon!

[blastfromthepast]

Originally Posted by Rubber Duck

The full implementation of ccTLD has been effectively kicked into the long grass along with DNAME. It looks as though a small selection of ccTLD AND gTLD will be implemented as NS, in the very near future. This could be even better than DNAME, because it means that Chinese, Japanese and Russian at least could be implemented very soon!

In other words, the real IDNs consisting of IDN.IDN will be launched soon that will kick into the long grass any IDN.ascii that are now being held by speculators. Great news indeed.

[Rubber Duck]

Originally Posted by blastfromthepast

In other words, the real IDNs consisting of IDN.IDN will be launched soon that will kick into the long grass any IDN.ascii that are now being held by speculators. Great news indeed.

No because Mapping can also be done with NS. Two records one registry just like with .CN.

[Drewbert]

>The idea that ccTLD is going to be suited ultimately to an NS solution is dead in the
>water. Everyone is calling for implementation of what is "ready to go".

Huh? NS is pretty much "ready to go".

What they're talking about is NS with mirrored zone files for both the .ccTLD and the .iccTLD

[Rubber Duck]

That is right. No new Registries here. ICANN was never committed to offering them complete new registries. I don't think anyone is expecting it apart from perhaps the Russians, whose interpretation of "Ready to Go" is unlikely to be the same as everyone else's.

Dot Com or Dot Net could also equally be done with mirroring of NS zone for a small number of languages.

They are talking about Experimental NS records, but it not meaningful unless they bang in something that already has traffic.

Originally Posted by Drewbert

>The idea that ccTLD is going to be suited ultimately to an NS solution is dead in the
>water. Everyone is calling for implementation of what is "ready to go".

Huh? NS is pretty much "ready to go".

What they're talking about is NS with mirrored zone files for both the .ccTLD and the .iccTLD

[Alphamale]

errr

wtf is going on

is it just me who is very confused

[Fka200]

Originally Posted by Alphamale

errr

wtf is going on

is it just me who is very confused

Conversation @ DNL chat going on right now about what's happening. I don't really get it either...