Re: [ga] Re: anyone notice fallout from this?

[steinle@smartvia.de]

It is pure information which maybe looks like spam to you ;-)

John wrote about ICANN's introduction of colliding top level domains, especially about the .BIZ collider.
And I wrote that this cannnot happen in the .PRO name space.
RegistryPro introduces .med.pro , .law.pro and .cpa.pro later this year. But the .PRO TLD already exists in the Inclusive Namespace roots (ORSC, Pacific Root,...). This would mean colliding domain names!

But there is a solution: Someone was so wise :-) to reserve exactly the same domain names (.law.pro, .med.pro, .cpa.pro) in the (registry reserved! ;-)).

This has following benefits:
ICANN people always talk about Stability of the Internet and about Security. Now you can have it!
1. .PRO is a "non-colliding" TLD unlike .info and .biz
2. Professionals could register IDENTICAL domain names in the "legacy root" and in the Inclusive Namespace root. Therefore users could get the same information whether they surf the "legacy root" or the Inclusive Namespace roots.
3. Because IDENTICAL sites with domain names registered in two registries exist in the "legacy root" and in the "Inclusive Namespace roots" there could be a complete data loss in one registry. Moreover one root network could go down completely. The domain name and the website would still be fully functional in the other root network! 
That's the benefit of redundancy. 
ICANN TALKS about Stability and Security of the Internet, others take action.
4. Security issues are paramont in the .PRO name space, it would be used by professionals like lawyers or accountants. If professionals would only register their domain name with RegistryPro the possibility that e-mails would reach their corresponding e-mail addrsss is approx. 95%. And you know these e-mails would very likely contain confidential information.
Therefore a 100% solution is needed. If professionals would register their domain name with both registries they could make sure that NO e-mail message would get lost. 


This was 100% information.
Maybe it is a problem for you William and Eric that I don't write about the solutions and actions of a third party or person.
If this would come from a third party/person this wouldn't be spam, right? ;-)


Best regards,
Simon

http://nic.pro.xs2.net
nic.PRO - the original .PRO third level domain registry!



> Yes that is pretty close to spam.  One could certainly make a case for it.
> Eric
> William X Walsh wrote:
> > Spam spam spam.
> >
> > Please keep it off the ga@dnso.org list.
> >
> > Tuesday, Tuesday, March 26, 2002, 3:47:48 PM, steinle@smartvia.de wrote:
> >
> > > In the dotPRO namespace there will be no colliders if all Registrants 
> register with http://nic.pro.xs2.net in addition!
> >
> > > Isn't that a great news!?
> >
> > > nic.PRO is supported by:
> > > - Common Interest Network Information Center Society
> > > - Name.Space
> > > - Open Root Server Confederation
> > > - The PacificRoot
> >
> > > check here for details:
> > > http://root-dns.org/VueDig/VueDig_tld.php?tld=nic.pro&record=NS
> >
> > > Best regards,
> > > Simon
> >
> > > http://nic.pro.xs2.net
> > > nic.PRO - the original .PRO third level domain registry!
> >
> > >> ----- Original Message -----
> > >> From: 'John R. LoVerso' <john@loverso.southborough.ma.us>
> > >> To: <usdom@lists.abuse.net>
> > >> Sent: Tuesday, March 26, 2002 3:26 PM
> > >> Subject: anyone notice fallout from this?
> > >> > ------- Start of forwarded message -------
> > >> > This document describes the 'Root Fix for the .US Top Level Domain'.  
> Root
> > >> > Fix is a series of actions taken by the Open Root Server Confederation
> > >> > (ORSC) to prevent the destabilization of the DNS due to ICANN's
> > >> > introduction of colliding top level domains.  This document describes 
> the
> > >> > actions taken bythe ORSC to remedy the collateral damage that has been
> > >> > directly caused to the .US top level domain in non-ICANN root systems.
> > >> >
> > >> > A URL for this Internet-Draft is:
> > >> >
> > >> http://www.ietf.org/internet-drafts/draft-higgs-schneiders-root-fix-
> us-00.tx
> > >> t
> > >> > ------- End of forwarded message -------
> > >> Lets get something straight.
> > >> 1. ORSC and Inclusive Namespace roots did not cause this problem, Neustar
> > >> did
> > >> by deliberatly moving the .US nameservers under BIZ.
> > >> 2. ICANN's versionof .BIZ is the collider.
> > >> No damage has been done that hasn't already been fixed.
> > >> John
> > >> ---
> > >> AGN Domain Name Services
> > >> http://www.adns.net
> > >> Censorship-Free GA list: http://dns-o.org/listinfo/ga
> > >> --
> > >> 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
> >
> > > --
> > > This message was passed to you via the ga-full@dnso.org list.
> > > Send mail to majordomo@dnso.org to unsubscribe
> > > ('unsubscribe ga-full' in the body of the message).
> > > Archives at http://www.dnso.org/archives.html
> >
> > --
> > Best regards,
> > William X Walsh <william@wxsoft.info>
> > --
> > Save Internet Radio!
> > CARP will kill Webcasting!
> > http://www.saveinternetradio.org/
> >
> > --
> > 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
--
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