Re: [lac-discuss-en] Re "Introduction of Two-Character Domain Names in the New gTLD Namespace" Public comment

Well, there can only be a fixed number of permutations (676) for possible
use in ISO 3166 since ISO 3166 can only be ASCII letters from aa to zz. And
while there may not be a rapid number of changes, there have been changes
to ISO 3166 in the past 10 years.

For example in 2010, for example :
http://www.iso.org/iso/iso_3166-1_newsletter_vi-8_split_of_the_dutch_antilles_final-en.pdf

BQ, CW and SX were added for Bonaire, Saint Eustatius and Saba , CuraÃao
and Sint Maarten (Dutch part) in the Caribbean.

Dev Anand





On Thu, Jul 10, 2014 at 8:47 AM, Carlton Samuels <carlton.samuels@xxxxxxxxx>
wrote:

> Closely reasoned and from the principle of cc assignment certainly worthy
> of the ALAC's consideration.
>
> While we're at it, lets consider that 3-character country codes are
> possible.
>
> Giving protection for a future event suggests we have a definite knowledge
> of country/territory breakdown and thusly, possible code assignment.  Tying
> up all permutations of 2 characters especially when you consider IDNs would
> be a tough sell.
>
> Carlton
> ---------'--------''-----
>
> On Jul 10, 2014 2:04 AM, "Dev Anand Teelucksingh" <devtee@xxxxxxxxx>
> wrote:
> >
> > Regarding the public comment on "Introduction of Two-Character Domain
> Names
> > in the New gTLD Namespace" at https://community.icann.org/x/VqzhAg
> > which ends July 10 2014, I've posted the following at
> > https://community.icann.org/x/VqzhAg
> > for consideration:
> >
> > "Various registries for multiple gTLDs are applying for exceptions to
> > Specification 5, Section 2 of the New gTLD Registry Agreement
> > ("Specification 5") with some registries suggesting the release of 2
> > character ASCII labels not on the current ISO 3166 standard would
> suffice.
> >
> > While this seems harmless, there is a possibility of new countries and
> > territories being created, and then allocated a new two character ASCII
> > label by ISO 3166/MA (see
> >
> https://web.archive.org/web/20111101141651/http://www.iso.org/iso/country_codes/iso-3166-1_decoding_table.htm
> > ).
> >
> > Any new country or territory created after 2014 would therefore not
> receive
> > the same protection as those in the 2014 ISO 3166-2 list and would find
> > that their new 2 character label is "given away", should they wish for
> > their 2 character ASCII label to be protected, as per Specification 5.
> >
> > Now, should the principle established by Specification 5 protecting 2
> > character ASCII labels even be in the New gTLD Registry Agreement? Many
> > would say, especially given the prevalence of two character labels in
> > existing TLDs like .com, .org and .net that this principle shouldn't be
> > applied to new gTLDs.
> > However, this (IMO) is a separate issue to the question being asked for
> in
> > the public comment.
> >
> > If Specification 5 is meant to defend the principle that country codes in
> > ISO 3166-2 should be protected in new gTLDs, then it should be enforced
> to
> > ensure future countries and territories with new 2 character ASCII labels
> > are protected in the same way as those territories and countries in
> today's
> > ISO 3166-2 list.
> >
> > Therefore, the proposals by Donuts for 143 of its new gTLDS, .kred by
> > KredTLD Pty Ltd, .best by BestTLD Pty Ltd and .ceo by CEOTLD Pty Ltd.
> > should be turned down in keeping with the principle of Specification 5.
> >
> > The proposal by .wiki by Top Level Design LLC which specifies that the
> two
> > character ASCII labels will only be used for languages identified by ISO
> > 639-1 does appear to meet the threshold that the use will not be confused
> > with the corresponding country codes, as per Specification 5 and could be
> > approved.
> >
> > Similarly, the proposal by .globo by Globo ComunicaÃÃo e ParticipaÃÃes
> S.A
> > which proposed the use of two character ASCII labels that are not letters
> > or by two characters where only one of the character is a letter are
> labels
> > that would not be used by ISO 3166-2 and could be approved."
> >
> > Thoughts?
> >
> > Kind Regards,
> >
> > Dev Anand Teelucksingh
> > _______________________________________________
> > lac-discuss-en mailing list
> > lac-discuss-en@xxxxxxxxxxxxxxxxxxxxxxx
> > https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en
>
>
_______________________________________________
lac-discuss-en mailing list
lac-discuss-en@xxxxxxxxxxxxxxxxxxxxxxx
https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-en