[At-Large] [IDN-WG] The New gTLD Progam in CLASS IN is no more a swindle

JFC Morfin jefsey at jefsey.com
Thu Jan 12 01:06:16 UTC 2012

At 18:07 11/01/2012, Avri Doria wrote:
>Two questions on this.

Hi! Avri,
I will try to collect the questions raised and answer to produce and 
maintain an IUTF FAQ.

>- wouldn't he be looking for support of these new Classes in 
>addition to Class IN, not instead?

This is something the user is to decide in the way he/she config the 
ML-DNS. A class is like a language: a way to describe the network 
topology which is built by the addresses. There may be conflicts and overlaps.

For exemple, let take the CLASS "FM" for families. Existing 
registries could have a filtered version of their "IN" CLASS registry 
pn their "FM" CLASS IRN (International Root Name) server.

>- doesn't this break because DNS Alias records pay no attention to 
>Class and therefore aliased names would collide despite being in 
>different classes?

Lutz has addressed this.

The IUTF basic principle is that what is a "MUST" decided by the IETF 
is a "IS" for the IUTF, something it is totally unable to change. 
CLASSes are of the essence of the IDNS for 40 years (even before the 
Internet). IDNS also initially included a reroute capacity as in the 
MX case, which might be of interest in the Web 2.0. Some other ideas 
may emerge. However, they can only come in addition, not as 
alternatives, and be operated in subsidiarity. This means also that 
not a single bit is to be changed in the underlaying protocols.


>On 11 Jan 2012, at 11:47, Lutz Donnerhacke wrote:
> > On Wed, Jan 11, 2012 at 04:32:48PM +0100, JFC Morfin wrote:
> >> This simply means that for each ".abcd" top-zone IDNgTLD paid K$ 185++
> >> to ICANN, there can be 65,535 other ".abcd" top-zones in the DNS. Some
> >> will be immediatel because the IUTF is going to accept a few CLASSes
> >> for family protection, customer documentation, testing of third party
> >> applications, etc.
> >
> > You only need to register the CLASS according to RFC6195 Section 3.2.
> >
> > Then you need to distribute an additional "root hint" file pointing to your
> > new root servers (similar to http://www.internic.net/domain/named.root)
> > As you can see, they only claim to be responsible for ./IN.
> >
> > Then you can start selling domains from your new root.
> >
> > Please allow me to add a professional advice. If you try to convince the
> > browser manufacturers to ask for your class instead of IN, you might have a
> > real market.
> >
> > --
> > Lutz Donnerhacke
> > Maintainer of the TLD bofh.

More information about the At-Large mailing list