Hi Jim -- YaButt -- Your 128 bit Universe is orthogonal (at this time) to our poor old 32 bit toy Internet. Besides, I am pushing the point that the conflict remains because of TICANNic insularity (head in sand,) and fear of recognizing ORSC;-)... I am not a .biz domain holder, and have no interest in being one. I have all the name space I need (for now) with NMA.COM. I understand your position and have no problems with it. I am just not prepared to play with it. Cheers...\Stef At 7:04 PM -0500 8/6/02, Jim Fleming wrote: >http://www1.ietf.org/mail-archive/ietf/Current/msg16912.html >----- Original Message ----- >From: "Einar Stefferud" <Steflist@thor.nma.com> > > > > We need to note the fact of the collision around .BIZ, and we are > > ready to discuss ways to resolve it any time ICANN (or its .BIZ > > Franchisee) wishes to engage in serious discussions. >========= > >Stef, > >What "collision around .BIZ" are you referring to ? > >Each SLD.BIZ owner that currently desires to participate in the >"toy" 32-bit IPv4 Proof-of-Concept (POC) experiments is free to >do so. That will build a base of .BIZ owners. There may be 50 or 60 >thousand serious .BIZ owners at some point. Those owners can then >work together to move beyond the experimental POC .BIZ testing, >to 128-bit DNS .BIZ services. Name-by-name, the SLD.BIZ namespace >can take shape and grow, with no collisions. Collisions at the SLD.TLD >POC level are ignored (i.e. rejected) in the 128-bit DNS. There can be >no so-called collisions, unless people support improperly configured >servers. A serious 128-bit DNS .BIZ Registry would not support that, >and the software prevents it. > >Looking at the .BIZ TLD server clusters below, in the dominant 32-bit >DNS providers, one can see that an SLD.BIZ owner simply has to make >sure that pointers to their nameservers are in all of the TLD clusters below >to make sure they are coherent in this early testing phase, also called, the >Proof-of-Concept phase. It is a way to boot-strap the .BIZ TLD and to >find interested owners. Are you a serious .BIZ owner ? > >Looking at the technical aspects of the information below, one can clearly >see that there is a reliability flaw in the usage of the .BIZ TLD to >support itself. >TLD Clusters should use a mixture of other TLDs to make sure that they do >not collapse under a shared fate scenario, or a >single-point-of-corporate failure. >As an example, a more robust TLD Cluster will have servers from .COM, .NET, >and some of the more stable TLDs. Using all of the same TLD and the same >TLD as the TLD itself, is a very bad idea. With lawyers designing TLD server >arrangements, rather than engineers, that sort of thing can happen. >This why .BIZ >is only in the Proof-of-Concept experimental phase. No serious >telecommunications >engineer would allow such a configuration to be part of critical >infrastructure. > >Since the mid-90s, the .BIZ TLD has grown from nothing to what it is today. >It clearly has a long way to go before being considered ready for 128-bit DNS >deployment. It may get there or it may not. The marketplace and the technology >can rapidly pass companies by, that do not keep up or keep pace. > >Jim Fleming >2002:[IPv4]:000X:03DB >http://www.iana.org/assignments/ipv4-address-space >http://www.ntia.doc.gov/ntiahome/domainname/130dftmail/unir.txt >0:212 BIZ > >====================================================== > >http://root-dns.org/vuedig/vuedig_tld.php?record=NS&tld=BIZ&submit=Submit >.BIZ - NS Resource Records. >Click on any NS RR link below to do a ServerScan. > >ANIC : AlterNIC : 160.79.129.192 >VueDig Results : Answer = 6 : Authority = 0 : Additional = 3. >BIZ. 6D IN NS c.gtld.BIZ. >BIZ. 6D IN NS d.gtld.BIZ. >BIZ. 6D IN NS e.gtld.BIZ. >BIZ. 6D IN NS f.gtld.BIZ. >BIZ. 6D IN NS a.gtld.BIZ. >BIZ. 6D IN NS b.gtld.BIZ. > >BORN : Business Oriented Root Network : 213.70.103.18 >VueDig Results : Answer = 6 : Authority = 0 : Additional = 6. >BIZ. 2D IN NS C.GTLD.BIZ. >BIZ. 2D IN NS D.GTLD.BIZ. >BIZ. 2D IN NS E.GTLD.BIZ. >BIZ. 2D IN NS F.GTLD.BIZ. >BIZ. 2D IN NS A.GTLD.BIZ. >BIZ. 2D IN NS B.GTLD.BIZ. > >CINICS : Common Interest Network Information Center Society : 216.15.192.130 >Result = No Response > >iDNS : i-DNS.net International : 208.184.174.7 >VueDig Results : Answer = 6 : Authority = 0 : Additional = 6. >BIZ. 2D IN NS E.GTLD.BIZ. >BIZ. 2D IN NS F.GTLD.BIZ. >BIZ. 2D IN NS A.GTLD.BIZ. >BIZ. 2D IN NS B.GTLD.BIZ. >BIZ. 2D IN NS C.GTLD.BIZ. >BIZ. 2D IN NS D.GTLD.BIZ. > >LRS : Legacy Root Servers : 198.41.0.4 >VueDig Results : Answer = 6 : Authority = 0 : Additional = 6. >BIZ. 2D IN NS F.GTLD.BIZ. >BIZ. 2D IN NS A.GTLD.BIZ. >BIZ. 2D IN NS B.GTLD.BIZ. >BIZ. 2D IN NS C.GTLD.BIZ. >BIZ. 2D IN NS D.GTLD.BIZ. >BIZ. 2D IN NS E.GTLD.BIZ. > >NSpace : Name.Space : 209.48.2.11 >VueDig Results : Answer = 0 : Authority = 1 : Additional = 0. >.BIZ not found. > >Nnet : New.net Inc : 206.132.100.42 >VueDig Results : Answer = 0 : Authority = 6 : Additional = 6. >BIZ. 1D IN NS B.GTLD.BIZ. >BIZ. 1D IN NS C.GTLD.BIZ. >BIZ. 1D IN NS D.GTLD.BIZ. >BIZ. 1D IN NS E.GTLD.BIZ. >BIZ. 1D IN NS F.GTLD.BIZ. >BIZ. 1D IN NS A.GTLD.BIZ. > >ONIC : The OpenNIC Project : 131.161.247.226 >VueDig Results : Answer = 4 : Authority = 0 : Additional = 4. >BIZ. 2D IN NS ns4-pacroot.opennic.glue. >BIZ. 2D IN NS ns1-pacroot.opennic.glue. >BIZ. 2D IN NS ns2-pacroot.opennic.glue. >BIZ. 2D IN NS ns3-pacroot.opennic.glue. > >ORSC : Open Root Server Confederation : 199.166.24.1 >VueDig Results : Answer = 3 : Authority = 0 : Additional = 3. >BIZ. 1H IN NS NS.ROOTFIX.NET. >BIZ. 1H IN NS NS1.ADNS.NET. >BIZ. 1H IN NS NS2.ADNS.NET. > >ORSN : Open Root Server Network : 217.146.140.67 >VueDig Results : Answer = 0 : Authority = 6 : Additional = 6. >BIZ. 2D IN NS F.GTLD.BIZ. >BIZ. 2D IN NS A.GTLD.BIZ. >BIZ. 2D IN NS B.GTLD.BIZ. >BIZ. 2D IN NS C.GTLD.BIZ. >BIZ. 2D IN NS D.GTLD.BIZ. >BIZ. 2D IN NS E.GTLD.BIZ. > >TINC : The Internet Namespace Cooperative : 64.6.65.10 >Result = No Response > >TPR : The PacificRoot : 204.107.129.2 >VueDig Results : Answer = 2 : Authority = 0 : Additional = 2. >BIZ. 2D IN NS ns2.adns.net. >BIZ. 2D IN NS ns1.adns.net. >=============================================