Re: [ga] Death Struggle in Name Space

[PacificRoot Hostmaster <idno@tallship.net>]

Charles,

You've missed the point. yet it appeared to me that Roeland had quite
eloquently explained it. This may in fact be a shortcoming of Roeland,
myself, and others here who sufficiently understand the nature of DNS in
te first place.

So I'll just point out a couple of things for you and attempt to bring you
up to speed....


On Sat, 14 Apr 2001, John Charles Broomfield wrote:

> 
> So, if I understand you correctly, what you're saying is that the ICANN
> action of adding their own ".biz" to their own root-zone (the one which you
> guys download from rs.internic.net), actually messes up the way that you
> later add to to it.

No, it wouldn't 'mess' anything up with us technically or operationally
from the standpoint of The PacificRoot rootzone. The ICANN .BIZ simply
couldn't make the muster because there is a pre-existing TLD string in 
the rootzone (The authorized one if you must have it that way) that
belongs to ARNI.

In continuing, we 'fetch' TLD zonedata from all over the world, and the
ICANN TLDs are only some of them. They have a right in our eyes to exist
there and not be interfered with by colliders. Therefore we would not be
willing to load the .ORG that Sandy Harris is operating.

We also load all of the ccTLDs, and tlds from independants as well as
other root systems. You see, it's really all about TLDs, and not roots.
The roots can't collide because there is only one name space - it's when
you have duplicate TLD strings in that one name space that you have
collisions, and technically that would be whether they existed in
different roots or in the same root, which I have seen before in the ORSC
root. .FILM is one example, existing simumltaneously in the same root with
the TLD servers listed from completely different zones - sometimes one
would work and sometimes the other. It was really extremely entertaining,
but I tired of experimenting with it after about four months and finally
pointed it out to their very embarrased rootzone manager.

In the meantime I had the privilege of studying in detail the nature of a
live collider. I gathered a lot of data  even though ORSC is not a
commercial grade production rootzone. very entertaining, or scary stuff
depending upon how you choose to view it.

So no, the foundation of The PacificRoot's rootzone is not the ICANN root,
but rather, The PacificRoot's root servers. Everything else is built
around that. ICANN's root is really for the most part a non-issue wrt
building our rootzone, we merely include their operational, non-colliding
TLDs.

> 
> Interesting concept that you decide to use the USG authoritative as long as
> it doesn't change, but if it DOES change, then you scream about it.
> 

um.... no.

Please go back to my tutorial yesterday when I explained
"X.GTLD-SERVERS.NET" That's what is authoritative for the ICANN TLDs, and
in The PacificRoot we point to those TLD Servers as Authoritative (You
have used the correct syntax though,  most lay people confuse AUTH with
authorized).

They can change their zonedata for the zones we choose to carry anytime
they like - after all it's their zone. The TLD doesn't have much of
anything to do with the root, except that it's served by it. And we do a
better job of that at The PacificRoot anyway :)


> Of course, one must understand that the amount of individuals that this
> actually affects (ie the ones that resolve through some method that actually
> adds things to the generic vanilla USG/ICANN root) is rather minimal (what
> was the last good count on it? less than .5% of the 'net?), and to take it a

um..... :) that's a big number when you start adding all those zeros
behind it ;) And if it breaks things - it's everyone on the planet that is
potentially effected.

> step further, this would then only REALLY affect those people who actually
> use a domain name under ".biz" which is visible through those alternative

No, both sides of the fence.

> actually on an operational basis (I defy ANYONE to show me someone that will
> really be affected by the introduction of ".biz" into the USG/ICANN roots,

http://www.icbtollfree.com/article.cfm?articleId=5146 will lead you to a
long list of people that will be happy to engage your defiance.

It seems that you understand nothing whatsoever about distribution channels  
in capitalist society, where a free market based economy is like a house
of dominoes. For if you did your wouldn't switch feet like that.

I'm inclined to actually sit down with you and show you how this all works
if you're truly as serious as you come off, but I'm a businessman and you
will have to, after all, agree to pay me.

> 
> Now, if you actually do think that there is a customer base out there who
> actually uses the non-ICANN ".biz" on a daily basis, then what is your
> problem with the ICANN one, as your CURRENT user base will continue to use
> their old one without a hitch!
> 

Collisions. You see, people such as yourself that are smart enough to
upgrade their machines in a timely manner don't run stuff like Microsoft
Internet Explorer version 1 or 2, and hopefully not 3. If you did you
wouldn't be able to see a vast portion of the Internet's name space now
would you? 

So you upgraded your system enabling you to see the whole Inernet.
Simple concept. It just makes sense. You see John Charles, it's not a
question of "IF", but instead it is a question of "WHEN", you will next
upgrqade your system to see the whole Internet by upgrading from the
deprecated, ICANN legacy system to the "Inclusive Name Space". It just
makes sense.

And when your friends and family give you email addresses that bounce on
you it is you who will suffer, because it just made sense to them and all
their other friends and relatives can now take advantage of the
availabilty of short, meaningful, and inexpensive domain names free from
arbitrary theft by ICANN.

You still use punched cards and mag tape John Charles?

> You can't have it both ways:
> -either you consider ICANN as authoritative and you decide to add to

Your still not getting this. perhaps an O'Reilly book would be good right
about now. I'll recomend DNS and BIND. Then you will be ready to play in
the sandbox.

Listen Very closely k? 

ICANN is not authoritative for a zone - a nameserver is. A nameserver is a
machine, and ICANN is a bunch of drycleaned, pressed, unelected, and
larcenous collusion artists. There is a big difference. One will answer
True or False - can you tell which one?


> -or your consider YOURSELF to be authoritative and say to hell with ICANN,
>  and play in your own sandbox with whatever names you want.

Nonsense. there is but one name space. The PacificRoot merely points to
the nameservers that are auth for all Known, non-colliding, and 
operational TLDs on the Planet.

The difficulty you are having is in the definition of "What is a
Collider?"

> 
> Of course, you've probably realized that considering yourself authoritative

Machines are authoritative for zones not companies. Please take the time
to educate yourself before using incorrect terminology that must
continually be corrected. You are almost not making sense. 


> you try to do a 50% stand and somehow convince the rest of the world that
> you are just as trustworthy as ICANN, so your own TLDs should be taken into

um... ICANN Trustworthy? hm... JUMBO Shrimp? hm.. DEAFENING Silence?

ROFLMAOPMP

http://www.law.com/ci-bin/gx.cgi/Appt.ogic+FTContentServer?pagename=law/View&c=Article&cid=ZZZ30K9I8LC&live=cst=1&pc=0&pa=0

> 
> At the base of it, there can only be ONE authoritative root-zone. You say

Wrong. There can only be one name space. Duplicate strings means
collisions. There "ARE" "MANY" authoritative rootzones pointing to
authoritative TLD zones pointing to authoritative SLD zones pointing to
authoritative 3LD zones etc...

> that the ICANN one is done without co-operation. What you mean is that YOU
> didn't get to have a disproportionate amount of say in it, but there has

Wrong as rain going up. Like Vint Cerf 'eventually' admitted to Congress,
They're only responsible for their own root. What he continually refused
to answer was that they have a responsibility to avoid collisions in the
name space that would harm or otherwise interfere with others, and that in
loading a collider that is exactly what they would do to ARNI's .biz and
everyone else that uses DNS for resolution.

It's like the Blue Belly's and the Rebs lining up agin' each one another
in the field and firing their musketts into the uniforms of the other. No
one asked ICANN to secede from the Union and dawn the Confederate Uniform
but they did and the bodies are just going to pile up until they
surrender.

Again, you forget that other Governments Have had it with them too and
have fired up Inclusive Roots and/or TLD servers elsewhere, and they're 
not going away either. You might as well face it John Charles, Atlanta is
already burning, Tecumseh is roasting marshmallows, and The PacificRoot is
here to stay :)

http://english.peopledaily.com.cn/200102/05/eng20010205_61600.html

Kindest regards,

Bradley D. Thornton
Chief Technology Officer
The PacificRoot/Joint Technologies Ltd.
The ONLY root that resolves all roots!
Upgrade your DNS today for FREE at:
http://www.PacificRoot.com
http://www.JointTech.com

--
This message was passed to you via the ga@dnso.org list.
Send mail to majordomo@dnso.org to unsubscribe
("unsubscribe ga" in the body of the message).
Archives at http://www.dnso.org/archives.html