See link below for the entire publication. Provided below is an excerpt from
the publication.Impact Of Alternative Roots In DNS
The following
examples show the impact to the DNS from a multiple
root zone environment.
It should be noted that each root zone, as
a singular entity, is
fully compliant with RFC2826. The problems
described in RFC2826
surface when the user has no ability to
determine which root zone
is being used for a particular
transaction.
Each
example also is marked as "STABILIZING" or "DESTABILIZING".
This
is an important concept to grasp. The primary fallacy that
must
be overcome is contained in the following set of statements:
"If a non-ICANN root service mounts a new TLD without ICANN
permission, this is defined to be destablizing."
and
"If ICANN corrects this situation
by adding a conflicting TLD
to the ICANN ROOT,
this is defined to be stabilizing."
There's no other way to say this:
THE ABOVE STATEMENTS ARE WRONG!
The fact is that there is no conflict
and no harm to the internet
until the 2nd version of a given TLD
(the duplicate) is created.
In order to remedy this, the correct
statements are as follows:
1. If any root service mounts a
new TLD which does not conflict
with a pre-existing
TLD, this SHOULD be defined as
stabilizing.
2. If any root service mounts a new TLD which conflicts with a
pre-exisitng TLD, this SHOULD be defined as destabilizing.
Therefore, any new TLD which conflicts with a pre-existing TLD is
destabilizing, no matter where it comes from. The following
examples illustrate which is correct, and which is not correct:
Example 1 (STABILIZING):
ICANN
Alt
root root
/|\
/|\
/ | \
/ | \
/ | \
/ | \
/ | \ /
| \
/ | \
/ | \
.com............ .com....... .biz
Example 1 does
not create any TLD conflicts. The Alternate Root,
has been enhanced
by the inclusion of the .biz TLD. Both roots
use the legacy root,
now maintained by the US Government (ICANN
root), as the baseline.
Example 2 (STABILIZING):
ICANN
Alt
Alt
root root(A)
root(B)
/|\ /|\
/|\
/ | \
/ | \ / | \
/ | \
/ | \ /
| \
/ | \
/ | \
/ | \
/ | \ / |
\ / |
\
.com............ .com....... .biz(A)
.com....... .biz(A)
Example 2 does not create any TLD
conflicts. Both Alternate Root A
and Alternative Root B have been
enhanced by the inclusion of the
.biz(A) TLD. The important thing
to note is that the same .biz TLD
is supported by both Alternative
Roots. All roots use the legacy
root, now maintained by the US Government
(ICANN root), as the
baseline.
Example 3 (DESTABILIZING):
ICANN
Alt
Alt
root
root(A)
root(B)
/|\
/|\
/|\
/ | \
/ | \
/ | \
/ | \ / |
\ / | \
/ | \
/ | \
/ | \
/ |
\ / | \
/ | \
.com............ .com....... .biz(A) .com.......
.biz(B)
Example 3 creates a TLD conflict. Both Alternate Root A and
Alternative Root B have .biz TLDs, but these TLDs are not
coordinated, or peered, and therefore duplicate zones may exist.
Note that all roots use the legacy root, now maintained
by the US
Government (ICANN root), as the baseline.
Example 4 (DESTABILIZING):
ICANN
Alt
Alt
root
root(A)
root(B)
/|\
/|\
/|\
/ | \
/ | \
/ | \
/ | \ / |
\ / | \
/ | \
/ | \
/ | \
/ |
\ / | \
/ | \
.com........biz(C) .com....... .biz(A) .com....... .biz(A)
Example 4 creates a TLD conflict. Both Alternate Root A and
Alternative Root B have been enhanced by the inclusion of the
.biz(A)
TLD. These .biz TLDs are coordinated (or peered) and are
conflict
free. Adding a different .biz(C) TLD to the ICANN root
causes a
conflict, and therefore duplicate zones may exist. Note
that all
roots use the legacy root, now maintained by the US
Government (ICANN
root), as the baseline. As you can see, this
example causes a bigger
(META) problem, in that it changes the
supported baseline of TLDs
that all the other roots are supposed
to recognize.
Alternate Roots do in fact exist. No one can prevent them from
existing,
because the selection of a root zone to point to is a
voluntary
act by DNS name server administrators and end-user
client software.