Re: ISO-3166 TLDs

[Simon Higgs <simon@higgs.com>]

At 11:25 PM -0500 12/29/96, Scott Bradner wrote:

I vote to modify the charter to this end. I do not believe it is too
late to do this.

It is important that the name space be addressed as a whole (or
"."/root). Creating policy for one aspect of the name space and not
another has the long term effect of fragmenting the name space
politically and socially. This will have the unfortunate repercussion
of creating irreversable technical fragmentation of the internet. Early
signs of this fragmentation can be seen in the form of various firewall
and proxy services being constructed by various international presences
to control access. While it may not be possible to prevent this type of
localized occurance, the I* organizations (including the IAHC) *MUST*
present a consistent policy across the name space for *ALL*
organizations providing registration services. In true IETF tradition,
compliance is always voluntary, but the policy must be there or
compliance will be non-existant.

> a number of people have asked why the IAHC has not addressed the
> assignment &/or operation of the ISO-3166 TLDs.
>
> from the IAHC charter
>
> --
> Each registry in the
> hierarchy is delegated authority from the registry above. A
> number of "Top Level Domain" (TLD) registries already exist:
> one for each country, and a small number which are
> international (iTLD) such as .com, .org and .net.
>
> . . .
>
> IAHC is an international multi-
> organization effort for specifying and implementing policies
> and procedures relating to iTLD.
> ---
>
> i.e. addressing the ISO-3166 TLDs is outside of the IAHC charter
>
> some might argue that it should not have been but in any case it is
>
> Scott


Regards,

Simon

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