The Internet+ fringe to fringe context of the ICANN end to end gTLD proposition
- To: new-gtld-applicant-support-handbook@xxxxxxxxx
- Subject: The Internet+ fringe to fringe context of the ICANN end to end gTLD proposition
- From: IUTF Secretariat <secretariat@xxxxxxxx>
- Date: Wed, 11 Jan 2012 01:34:37 +0100
Every Internet engineer knows why the legal terms of the gTLD
proposition are technically incorrect. The first authority to
document it was ICANN in its eleven year old ICP-3 document. This
document asked the Internet community to experiment while leading up
to this very day when there would be "better architectures for
getting the job done, where the need for a single, authoritative root
will not be an issue".
This was tested by open sources for several years, discussed by lead
users within the IETF framework, and documented by the emerging IUse
(whole digital ecosystem [WDE] Intelligent Use) community, in turn
creating its own standardization body, which is the young IUTF.
As has been committed to for years, once IDNA2008 was published the
IETF matured its consequences and ICANN worked on the variants and
post-IDNA2008 issues at the end to end Internet layers, we now
document the fringe to fringe people centric Internet+ Architectural
Framework for network extended and intelligent services. It is in
this way that the network architecture will be able to match the WSIS
unanimous international demand for a person-centric Information Society.
An IETF Draft will be published in the coming hours using the IUTF
text posted at:
(this order had to be followed to affirm the IP rights of the IUse
community). The target is to match the Internet+ requirement in order
to meet the IUsers' needs for trillions of domain names, attached to
billions of operational IPv6 addresses, most probably belonging to
millions of concerted international root names (IRNs).
We all know that the ICANN gTLD proposition includes some added value
in the end to end Internet CLASS IN. Our ongoing IETF Draft and
online document should help candidate gTLD registrants and TM holders
to consider the real situation of the whole digital ecosystem fringe
to fringe Internet+, its expected deployment transition, and the best
strategy for their organization in this nascent context along with
the protection of their rights.
NB.1. The Internet+ fringe to fringe architectural framework can be
discussed on the iucg@xxxxxxxx and iutf@xxxxxxxx mailing lists.
NB.2. This is what ICANN published on Jyly 9, 2001. It started the
processus of creation of the IUTF.
"Experimentation has always been an essential component of the
Internet's vitality. Working within the system does not preclude
experimentation, including experimentation with alternate DNS roots.
But these activities must be done responsibly, in a manner that does
not disrupt the ongoing activities of others and that is managed
according to experimental protocols.
"DNS experiments should be encouraged. Experiments, however, almost
by definition have certain characteristics to avoid harm: (a) they
are clearly labeled as experiments, (b) it is well understood that
these experiments may end without establishing any prior claims on
future directions, (c) they are appropriately coordinated within a
community-based framework (such as the IETF), and (d) the
experimenters commit to adapt to consensus-based standards when they
emerge through the ICANN and other community-based processes. This is
very different from launching commercial enterprises that lull users
into a sense of permanence without any sense of the foregoing
obligations or contingencies.
"Moreover, it is essential that experimental operations involving
alternate DNS roots be conducted in a controlled manner, so that they
do not adversely affect those who have not consented to participate
in them. Given the design of the DNS, and particularly the
intermediate-host and cache poisoning issues described in Section 1
above, special care must be taken to insulate the DNS from the
alternate root's effects. For example, alternate roots are commonly
operated by large organizations within their private networks without
harmful effects, since care is taken to prevent the flow of the
alternate resource records onto the public Internet.
"It should be noted that the original design of the DNS provides a
facility for future extensions that accommodates the possibility of
safely deploying multiple roots on the public Internet for
experimental and other purposes. As noted in RFC 1034, the DNS
includes a "class" tag on each resource record, which allows resource
records of different classes to be distinguished even though they are
commingled on the public Internet. For resource records within the
authoritative root-server system, this class tag is set to "IN";
other values have been standardized for particular uses, including
255 possible values designated for "private use" that are
particularly suited to experimentation.10
"As described in a recent proposal within the IETF,11 this "class"
facility allows an alternate DNS namespace to be operated from
different root servers in a manner that does not interfere with the
stable operation of the existing authoritative root-server system. To
take advantage of this facility, it should be noted, requires the use
of client or applications software developed for the alternate
namespace (presumably deployed after responsible testing), rather
than the existing software that has been developed to interoperate
with the authoritative root. Those who operate alternate roots for
global commercial purposes, however, have not followed this course.
"In an ever-evolving Internet, ultimately there may be better
architectures for getting the job done where the need for a single,
authoritative root will not be an issue. But that is not the case
today. And the transition to such an architecture, should it emerge,
would require community-based approaches. In the interim, responsible
experimentation should be encouraged, but it should not be done in a
manner that affects those who do not consent after being informed of
the character of the experiment."