At 08:17 PM 7/18/99 -0700, you wrote:
>At 10:30 PM 7/18/99 -0400, you wrote:
>>
>> At 07:25 PM 7/18/99 -0700, you wrote:
>> >At 06:51 PM 7/18/99 -0700, you wrote:
>> >>
>> >
>> >>
>> >>In other words, if there were to be established a viable non-ICANN root
>> >>system, then all this effort to establish advisory committees,
Supporting
>> >>Organizations, WIPO rules, ADR, taxes/fees, etc would all exist only on
>> >>those things willing to voluntarily accept the rules derived from the
>> >>ICANN root (and possibly the ICANN TLDs). Everyone and everything else
>> >>would be exempt.
>> >>
>> >> --karl--
>> >>
>> >Which certainly has its appealing aspects. But 'splain something: I'm
>> >sitting here on, say, a xxx.com or a xxx.net ISP, and I want to search a
>> >.per or a .biz, or more exactly I want to search on whatever, some of
>> >which may happen to be on .per or .biz. Alternatively, I want all the
>> people
>> >on .per and .biz to find my pages, of which (as happens to be the case)
>> >I have one on .com and another on .net. How do we communicate?
>> >Or are we existing as in the latest pseudo-physics fad, alternative
>> universes;
>> >coexisting in time and space but separated by a warp factor, a wrinkle in
>> >the continuum, or whatever?
>> >
>>
>> Bill, this is a simple one. The only problem is one of marketing.
>>
>> It is very easy to have your machine point to more than one (and in most
>> cases at least three) DNS servers. In a simple bifurcated root,
pointing to
>> two or three would likely do.
>>
>> It gets a bit more problematic (although certainly very easy to
overcome) if
>> there are multiple roots. One of the DNS servers could certainly be a
>> "resolving" root server, determining which root to which to refer. Another
>> approach would be to implement a heirarchically superior root syste ("super
>> root") which allows for root - then - TLD resolution.
>>
>> Of course, these are simple examples. But the solution is also simple.
>It is
>> a matter of coordinated agreement on which approach to use, then doing it.
>>
>> Again, the core problem is one of marketing. If a better mouse trap is
>> built, but no one knows of it or how to use it, nothing has been
>> accomplished.
>>
>> The technology is easy.
>
>
>And more or less as I had guessed. Each "owner" of an alternative TLD
>would be
>in some root, if all of .per, .biz,
>.whatever agreed to use a resolving root server or a super root, either of
the
>latter would connect to that other
>universe of .com, etc., , and the run-of-the-mill user like myself would be
>depending upon the operation of that
>resolving root or root server to route traffic to or from our own little
>domains with respect both to the ICANN
>roots and the alternative roots. Right? All of the alternative roots would
>have their equivalent of the present
>"A" registry run by NSI?
>
>I might add that "my machine" points to my ISP (europa.com), period, and as I
>recall it pointed to RainNet, etc.,
>but was bought out by "The Northwest Link Family" (and I neither know nor
care
>what that is all about) and will
>likely remain that way. I'm just the klutz at the end (and, to agree with
one
>post today, I am a PERSON and
>not a friggin' "consumer" :-) ).
Bill, you miss the point. Your ISP (europa.com) told you to set your DNS
server entries to some specific addresses when you signed up. Those
arbitrary entries are set within your computer's settings, and have little
to do with what ISP you are using.
If you are using a Microsoft product, you have the choice to add whatever
DNS servers you choose. Most *people* (not consumers) simply blindly put
the entries as provided by their ISP. You have the choice, however, as to
where you point. Again, it is a *marketing* issue - you are not aware of
how simple it is to do, and no *marketing* has been done to inform you as
to how it can be done.
It is an easy thing to demonstrate. Many users on this list are already
doing it.
Gene...
>
>And thanks.
>
>Bill Lovell
>
>
>>
>> Gene...
>> >Bill Lovell
>> >http://cerebalaw.com
>> >http://wend.net (not yet posted)
>> >
>> >
>> >
>> ++++++++++
>> Gene Marsh
>> president, anycastNET Incorporated
>> 330-699-8106
>>
>
>
>
>
>
++++++++++
Gene Marsh
president, anycastNET Incorporated
330-699-8106
