W3C home > Mailing lists > Public > public-egov-ig@w3.org > January 2012

Re: iso3166 delegations in the IANA root and associated properties (was: Re: ccTLD as ...)

From: Aisenberg, Michael A. <maisenberg@mitre.org>
Date: Wed, 11 Jan 2012 14:03:08 +0000
To: "'ebw@abenaki.wabanaki.net'" <ebw@abenaki.wabanaki.net>, "'public-egov-ig@w3.org'" <public-egov-ig@w3.org>
Message-ID: <31567E986892CE4CB48E725707EA268D0710FAA1@IMCMBX02.MITRE.ORG>
How do we reconcile Eric's "use of 'brand' is contrary to policy" with ICANN decision to permit "domains for hire" like .IRC or .BBC ?
Michael
M.A.A.  Sent from handheld

----- Original Message -----
From: Eric Brunner-Williams [mailto:ebw@abenaki.wabanaki.net]
Sent: Wednesday, January 11, 2012 08:32 AM
To: public-egov-ig@w3.org <public-egov-ig@w3.org>
Subject: iso3166 delegations in the IANA root and associated properties (was:  Re: ccTLD as ...)

First, the set of policies implemented by ccTLD registry operators is
non-uniform. Some have been repurposed as gTLDs, under the theory of
subsidiarity, and some of these are operated by Verisign, Afilias or
NeuStar. Some have the base gTLD registration policy (First Come,
First Serve) with the, or a minor variation of, the gTLD UDRP, and a
nexus requirement for the contact records (or or all of {registrant,
administrative, technical and billing contacts}) or the Name Servers.

Second, those which are not repurposed, e.g., us, bz, cc, co, in, me,
... differ in secondary structure, implementation, and registration
rules. As an example of the implementation variation, until recently
the .za registry was a registry of several independent secondary
registries.

I could go on, but the main points are that using the word "brand" is
contrary to the practice of delegated iso3166 code point name space
policy makers, registry operators, and their access providers and end
users, with the exception of those delegations which have been
captured for other than local public interest, and policy,
implementation, and utilization vary significantly.

Eric
Received on Wednesday, 11 January 2012 14:06:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 11 January 2012 14:06:36 GMT