ICANN ICANN Email List Archives

[gtld-guide]


<<< Chronological Index >>>    <<< Thread Index >>>

Specification 5

  • To: gtld-guide@xxxxxxxxx
  • Subject: Specification 5
  • From: Eric Brunner-Williams <eric.brunner@xxxxxxxxxxx>
  • Date: Tue, 25 Nov 2008 17:16:14 -0500

Where a registry provides registration for more than just the 2nd level, and which may be arbitrarily deep, particularly if the CRAI-1 model is allowed to be exploited, what is the utility of requiring the string "EXAMPLE" to be provisioned at each point in the namespace where the registry makes registrations?

What is the utility for reserving all two character labels, particularly those which do not correspond to territorial allocations by the iso3166MA?

How is the registry going to reach an agreement with the government and country-code managers for AP (African Regional Industrial Property Organization)?

For code points which are "Code element may be used without restriction" in iso3166? For code points which are "Code element deleted from ISO 3166-1; stop using ASAP"
For code points which are "Code element must not be used in ISO 3166-1"
For code points which are "Code element must not be used in ISO 3166-1?
For code points which are "Code element free for assignment(by ISO 3166/MA only!)"?

Commentary. This appears to be an excessive set of constraints, and vacant codepoints can't confuse with iso3166MA allocated code points, and while iso3166 isn't static, it doesn't wiggle around wildly either.

Eric Brunner-Williams


<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy