Clarification please (was Re: Is stuttering the price to pay?)

[Simon Higgs <simon@higgs.com>]

At 1:04 PM +0100 12/30/96, Werner Staub wrote:

Could somebody please clarify what is meant in the draft as there are
two distinct interpretations of .tm. One of them is completely
ludicrous, but seems to be the general understanding.

Can someone from the IAHC clarify the following paragraph:

          Addition of .tm.<iso3166-code>

          IAHC recommends that the functional name .tm.<iso3166-code>,
          or a local language equivalent thereof, be added to the
          functional name set documented in section 6.1.1 of this
          document, above, as described more fully in section 0 of
          this document (see below).

Does this mean literally .TM.<iso3166-code>, or .<tm-category>.<iso3166-code>?


> > > > - Why ".tm.int" when it can be ".tm"?
> > tm from a global perspective will have to be run by some sort of
> > International TM authority.  Therefore it makes sense to put it
> > under .int.
> >         .TM has the added property of being in the ISO 3166 list.
>
> I don't know how many names have already been registered for
> under .tm (Turkmenistan). Certainly not many. There is no
> problem in making an exception for Turkmenistan if there
> already is one for GB alias UK.
>
> The fact is that the word "tm" already has substantial
> "linguistic goodwill" as a trademark identifier, whereas .tm
> as a country identifier for Turkmenistan is practically unknown.
> The financial result of a .tm gTLD is bound to be _much_ better
> than a .tm.int . Some of that money can be used
> to improve Turkmenistan's connectivity, as a compensation
> for the problems with changing its TLD identifier.
>

Regards,

Simon

--
If at first you don't succeed, skydiving is not for you.