Comments on: The lives of country code domains http://blog.icann.org/2007/09/the-lives-of-country-code-domains/ Internet Corporation for Assigned Names and Numbers Mon, 23 Nov 2009 02:20:28 -0800 http://wordpress.org/?v=2.8.6 hourly 1 By: Domisfera » Articulo » The .rs domains of Serbia http://blog.icann.org/2007/09/the-lives-of-country-code-domains/comment-page-1/#comment-8956 Domisfera » Articulo » The .rs domains of Serbia Fri, 28 Dec 2007 23:33:10 +0000 http://blog.icann.org/?p=195#comment-8956 [...] and .me (Montenegro). It is envisaged this transfer will take a couple of years, and ICANN will monitor the [...] [...] and .me (Montenegro). It is envisaged this transfer will take a couple of years, and ICANN will monitor the [...]

]]> By: country » Comment on The lives of country code domains by Elaine http://blog.icann.org/2007/09/the-lives-of-country-code-domains/comment-page-1/#comment-5941 country » Comment on The lives of country code domains by Elaine Mon, 29 Oct 2007 15:31:36 +0000 http://blog.icann.org/?p=195#comment-5941 [...] the rest of this great post here [...] [...] the rest of this great post here [...]

]]> By: Elaine http://blog.icann.org/2007/09/the-lives-of-country-code-domains/comment-page-1/#comment-5795 Elaine Sat, 27 Oct 2007 16:46:05 +0000 http://blog.icann.org/?p=195#comment-5795 "How many .tp sites are still active, and how many of those don’t match the content of the corresponding .tl domains which are provided to registrants as a replacement?" This is a problem the registrant must resolve. During re-delegation all .tp names were mapped to .tl. By example, the exact record for domain.tp was copied and mirrored to domain.tl. Registrants of .tp names have been instructed to move content to their new .tl names. Existing .TP domains are expiring or have expired and cannot be renewed. When a registrant seeks to renew their .tp name, it is not possible. Instead they are instructed to move web content to the .TL version. It is neither a short-term project nor a difficult problem. “How many .tp sites are still active, and how many of those don’t match the content of the corresponding .tl domains which are provided to registrants as a replacement?”

This is a problem the registrant must resolve. During re-delegation all .tp names were mapped to .tl. By example, the exact record for domain.tp was copied and mirrored to domain.tl. Registrants of .tp names have been instructed to move content to their new .tl names. Existing .TP domains are expiring or have expired and cannot be renewed. When a registrant seeks to renew their .tp name, it is not possible. Instead they are instructed to move web content to the .TL version. It is neither a short-term project nor a difficult problem.

]]> By: Wibblemeister http://blog.icann.org/2007/09/the-lives-of-country-code-domains/comment-page-1/#comment-5097 Wibblemeister Fri, 12 Oct 2007 21:57:39 +0000 http://blog.icann.org/?p=195#comment-5097 BTW - when can we expect to see ccTLDs delegated for the new ISO 3166-1 codes of BL and MF? BTW – when can we expect to see ccTLDs delegated for the new ISO 3166-1 codes of BL and MF?

]]> By: Vasily http://blog.icann.org/2007/09/the-lives-of-country-code-domains/comment-page-1/#comment-4820 Vasily Sat, 06 Oct 2007 17:19:50 +0000 http://blog.icann.org/?p=195#comment-4820 I, as well as many Russians, for closing ICANN in Russia. Also I consider, that ICANN strikes at my rights. Yours faithfully, Vasily. I, as well as many Russians, for closing ICANN in Russia. Also I consider, that ICANN strikes at my rights. Yours faithfully, Vasily.

]]> By: Andrey G. Sergeev http://blog.icann.org/2007/09/the-lives-of-country-code-domains/comment-page-1/#comment-4817 Andrey G. Sergeev Sat, 06 Oct 2007 15:46:35 +0000 http://blog.icann.org/?p=195#comment-4817 <b>CarlB</b> <i>If .su were to be moved (in its entirety) to another TLD, then .cis (or its translated equivalent, Содружество Независимых Государств - СНГ) would be the more obvious candidate.</i> Nope. In fact CIS as an interstate entity is more dead than alive so they should first develop the <b>.CIS.INT<b> TLD rather than request a new one. CarlB
If .su were to be moved (in its entirety) to another TLD, then .cis (or its translated equivalent, Содружество Независимых Государств – СНГ) would be the more obvious candidate.

Nope. In fact CIS as an interstate entity is more dead than alive so they should first develop the .CIS.INT TLD rather than request a new one.

]]> By: David Conrad http://blog.icann.org/2007/09/the-lives-of-country-code-domains/comment-page-1/#comment-4739 David Conrad Fri, 05 Oct 2007 08:22:24 +0000 http://blog.icann.org/?p=195#comment-4739 That would be an issue to raise with the ISO-3166 Maintenance Agency, not with ICANN. That would be an issue to raise with the ISO-3166 Maintenance Agency, not with ICANN.

]]> By: Wibblemeister http://blog.icann.org/2007/09/the-lives-of-country-code-domains/comment-page-1/#comment-4738 Wibblemeister Fri, 05 Oct 2007 08:15:36 +0000 http://blog.icann.org/?p=195#comment-4738 Why should .bv and .hm (and others) not be included in ISO 3166-1? Bouvet Island is a dependency of Norway and not an integral part of the Kingdom, and whilst the Heard and McDonald Islands are a dependency of, rather than an integral part of the Commonwealth of Australia. If France wishes to integrate its various territories into France proper, that's entirely its business, but equally it's the business of other nations how they define their relationships with their dependent territories. Why should .bv and .hm (and others) not be included in ISO 3166-1? Bouvet Island is a dependency of Norway and not an integral part of the Kingdom, and whilst the Heard and McDonald Islands are a dependency of, rather than an integral part of the Commonwealth of Australia.

If France wishes to integrate its various territories into France proper, that’s entirely its business, but equally it’s the business of other nations how they define their relationships with their dependent territories.

]]> By: David Conrad http://blog.icann.org/2007/09/the-lives-of-country-code-domains/comment-page-1/#comment-4249 David Conrad Wed, 26 Sep 2007 07:19:47 +0000 http://blog.icann.org/?p=195#comment-4249 Carl, The decision as to whether SU is moved to "exceptionally reserved" is one made by ISO-3166/MA, not ICANN. To my knowledge, no one at ICANN has "threatened to 'nuke the Soviet Union' from the Internet". We have asked the community what we should do about the issue of codes, including SU, YU, and TP, that have been moved off ISO-3166-1 by ISO-3166/MA. In all cases but SU, agreements have been reached that allowed for a graceful transition to a new code. The question we face is what to do when a graceful transition is not possible. Regards, -drc Carl,

The decision as to whether SU is moved to “exceptionally reserved” is one made by ISO-3166/MA, not ICANN.

To my knowledge, no one at ICANN has “threatened to ‘nuke the Soviet Union’ from the Internet”. We have asked the community what we should do about the issue of codes, including SU, YU, and TP, that have been moved off ISO-3166-1 by ISO-3166/MA. In all cases but SU, agreements have been reached that allowed for a graceful transition to a new code. The question we face is what to do when a graceful transition is not possible.

Regards,
-drc

]]> By: David Conrad http://blog.icann.org/2007/09/the-lives-of-country-code-domains/comment-page-1/#comment-4248 David Conrad Wed, 26 Sep 2007 07:14:41 +0000 http://blog.icann.org/?p=195#comment-4248 Elisabeth, The approach you mention is not "Kim's" approach, it is the approach used by the IANA since the inception of the domain name system in 1983. Your comments about HM and BV appear to be irrelevant. ICANN does not instruct ISO-3166/MA, rather we listen to what they say. They have not moved HM or BV to transitionally reserved, so there is no issue. They say that uses of transitional codes should cease "ASAP" and that puts us in a bit of a bind with SU since it does not appear they are interested in ceasing "ASAP". You are implying we cease using ISO-3166-1 as a determinant for ccTLDs. That's fine if that's what the Internet community desires, but it would be helpful if you would suggest an alternative. Regards, -drc Elisabeth,

The approach you mention is not “Kim’s” approach, it is the approach used by the IANA since the inception of the domain name system in 1983.

Your comments about HM and BV appear to be irrelevant. ICANN does not instruct ISO-3166/MA, rather we listen to what they say. They have not moved HM or BV to transitionally reserved, so there is no issue. They say that uses of transitional codes should cease “ASAP” and that puts us in a bit of a bind with SU since it does not appear they are interested in ceasing “ASAP”.

You are implying we cease using ISO-3166-1 as a determinant for ccTLDs. That’s fine if that’s what the Internet community desires, but it would be helpful if you would suggest an alternative.

Regards,
-drc

]]>