Dear Nephew Ole;-)... You are showing great ignorance of how the ORSC (not alternate) root service works. If you want to discuss these issues with me, you will have to get yourself lined up to use the ORSC root service, and then you can tell me how it does not work for you. But all this idle speculation is simply silly and not the least productive. You have no basis to compare or determine what may or may not be true, so either get real or stop making a fool of yourself. And, take note, I do not tolerate the use of D'Crock's tools of EMail attack. I suggest that to remain in good standing as a nephew, you will refrain from such silly public attacks. You don't need to stop being friends with D'Crock. Just don't use his logic on me;-)... It is your choice to make, not mine;-)...\Stef At 2:46 PM -0700 7/30/02, Ole J. Jacobsen wrote: >But when the "navive user" has his or her config altered in this way, it >is likely to cause confusion and frustration when Joe can reach .STEF, >but Mary can't. > >Choice is a fine thing, incompatibility is not. > >Having one Internet is a good thing. > >Ole > > > >Ole J. Jacobsen >Editor and Publisher >The Internet Protocol Journal >Office of the CTO, Cisco Systems >Tel: +1 408-527-8972 >GSM: +1 415-370-4628 >E-mail: ole@cisco.com >URL: http://www.cisco.com/ipj > > > > >On Tue, 30 Jul 2002, Joe Touch wrote: > > > Einar Stefferud wrote: > > > ORSC does not support what NEW.NET is doing either, but please note that > > > this has nothing to do the lack of cooperation that ICANN exudes. > > > > Agreed. I was addressing Ole's point _only_, in two ways: > > > > 1) it's not so hard to modify a naive user's DNS at > > the browser or endhost configuration > > > > 2) your ISP may already be doing it by at the DNS > > layer > > > > How big an issue this is is distinct from how complex it is to achieve. > > > > Joe > > > >