<!-- MHonArc v2.4.4 --> <!--X-Subject: Re: [MUD-Dev] OT: NIS/AlterNIC and the DNS system --> <!--X-From-R13: Qnyvona Fverfvnf Rnexybpx <pnyvonaNqnexybpx.pbz> --> <!--X-Date: from fabius.globecomm.net [207.51.48.6] by in3.ibm.net id 870276375.83484-1 Wed Jul 30 15:26:15 1997 CUT --> <!--X-Message-Id: 33DF5D8D.42A4D74C#darklock,com --> <!--X-Content-Type: text/plain --> <!--X-Reference: 199707291511.PAA127970#out2,ibm.net --> <!--X-Reference: 3.0.2.32.19970729213013.00ae1690#mail,tenetwork.com --> <!--X-Head-End--> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <html> <head> <title>MUD-Dev message, Re: [MUD-Dev] OT: NIS/AlterNIC and the DNS system</title> <!-- meta name="robots" content="noindex,nofollow" --> <link rev="made" href="mailto:caliban#darklock,com"> </head> <body background="/backgrounds/paperback.gif" bgcolor="#ffffff" text="#000000" link="#0000FF" alink="#FF0000" vlink="#006000"> <font size="+4" color="#804040"> <strong><em>MUD-Dev<br>mailing list archive</em></strong> </font> <br> [ <a href="../">Other Periods</a> | <a href="../../">Other mailing lists</a> | <a href="/search.php3">Search</a> ] <br clear=all><hr> <!--X-Body-Begin--> <!--X-User-Header--> <!--X-User-Header-End--> <!--X-TopPNI--> Date: [ <a href="msg00289.html">Previous</a> | <a href="msg00291.html">Next</a> ] Thread: [ <a href="msg00282.html">Previous</a> | <a href="msg00296.html">Next</a> ] Index: [ <A HREF="author.html#00290">Author</A> | <A HREF="#00290">Date</A> | <A HREF="thread.html#00290">Thread</A> ] <!--X-TopPNI-End--> <!--X-MsgBody--> <!--X-Subject-Header-Begin--> <H1>Re: [MUD-Dev] OT: NIS/AlterNIC and the DNS system</H1> <HR> <!--X-Subject-Header-End--> <!--X-Head-of-Message--> <UL> <LI><em>To</em>: <A HREF="mailto:mud-dev#null,net">mud-dev#null,net</A></LI> <LI><em>Subject</em>: Re: [MUD-Dev] OT: NIS/AlterNIC and the DNS system</LI> <LI><em>From</em>: Caliban Tiresias Darklock <<A HREF="mailto:caliban#darklock,com">caliban#darklock,com</A>></LI> <LI><em>Date</em>: Wed, 30 Jul 1997 11:28:13 -0400</LI> </UL> <!--X-Head-of-Message-End--> <!--X-Head-Body-Sep-Begin--> <HR> <!--X-Head-Body-Sep-End--> <!--X-Body-of-Message--> <PRE> Jeff Kesselman wrote: > > BUT I thin kterhe IS a legitimate concern in the fact the the entire name > space is controleld by NIS at the moment. Thatw as fine when it was non > profit, mroe ro less, but nwo that theya re charging $100 a year for the > priveledge fo beign listed in their database, the space aught to be opened > i nan organzied and rationale way to comepting services. Register a .org domain, which costs nothing. You only need to pay if you are operating a commercial site... and it's only $50 a year. That's like $4.17 a month. It's a joke. They're not making any money off that, when you consider the 24-hour monitoring, backup systems, manpower, fat pipes, analysis, record keeping, they do a lot of stuff over there. It's not like setting up a single network. This is a definite SPF for the entire DNS system, and if they have downtime at *all* it creates a huge problem. Consider that all the .org and .edu and .gov sites are provided free to qualifying people, and you're looking at that $4.17 a month per commercial domain supporting ALL of the NIS domain services. <RANT> If you want to crucify someone for making money off essential services on the internet, look to the certification authorities and what payments they require for a digital certificate appropriate for secure internet-based commerce. They're not even real time service. A digital certificate fee is like charging someone a fee to sign their e-mail with your PGP key to prove that it's real e-mail. I'd be a lot more upset about that than I am about NIS charging me $4.17 a month for a domain name. </RANT> > I can't believe it woudl be that hard to modify the rpotocols to allow > multiple players in that arena. Here's what I see as the problem. While multiple players are certainly *possible*, someone somewhere needs to handle a single authority that determines which ones are official. You have to have a root directory. Right now, that's NIS. When people want to take advantage of the new top level domains, they have to point at the AlterNIC servers (which are incomplete and always somewhat out of date), or at the NIS servers (which don't support the new top level domains). If AlterNIC and NIS were talking to each other and trying to work things out, this wouldn't be too tough... but AlterNIC has been openly and consistently hostile to NIS, which isn't exactly greasing the wheels. Add to this the idea that AlterNIC is not exactly as technologically stable or capable as NIS, and NIS has a perfect reason to say "They are not stable; they are not effective; they are not ready. We cannot collaborate with them." Now that AlterNIC has added this childish stunt to their history, the good ideas behind it are more or less lost in the debate over whether you can trust AlterNIC with your information. <OPINION> I have a tentative solution: registration of individual top-level domains. NIS could handle the root server, the top-level domains could be registered to other companies, and those companies could charge what the market will bear for names within those domains. NIS could continue to handle the .com, .org, .edu, and .gov domains as usual, but now other companies could register appropriate top-level domains in their own servers. An AUP of sorts could be drafted for the existing domain names, specifically .com which I think should be further restricted to companies legally entitled to do business; for example, we have the well-known www.bluesnews.com for Quake news, which is not really a commercial site. The other top level domains already have appropriate AUPs of a sort. This could bring in the single most important Big Win of the AlterNIC concept: .xxx for pornographic sites. If all the pornographic sites were registered under .xxx, everyone wins. The pornhounds can find porn sites more easily. The parents can filter out all porn sites in a trice. The children can't claim they didn't know what was on it. And the government can collect accurate data on how much traffic porn sites get. (I don't think the American public realises just how many people really DO want porn on the internet.) </OPINION> The internet is due for a reorganisation. But it's not something we can do overnight, and it's not going to be without hardships and setbacks. The question is whether we're willing to bite the bullet and just do it. </PRE> <!--X-Body-of-Message-End--> <!--X-MsgBody-End--> <!--X-Follow-Ups--> <HR> <!--X-Follow-Ups-End--> <!--X-References--> <UL><LI><STRONG>References</STRONG>: <UL> <LI><STRONG><A NAME="00268" HREF="msg00268.html">Mail not getting to the list</A></STRONG> <UL><LI><EM>From:</EM> coder#ibm,net</LI></UL></LI> <LI><STRONG><A NAME="00282" HREF="msg00282.html">Re: [MUD-Dev] Mail not getting to the list</A></STRONG> <UL><LI><EM>From:</EM> Jeff Kesselman <jeffk#tenetwork,com></LI></UL></LI> </UL></LI></UL> <!--X-References-End--> <!--X-BotPNI--> <UL> <LI>Prev by Date: <STRONG><A HREF="msg00289.html">Re: [MUD-Dev] C&C and Event Rescheduling</A></STRONG> </LI> <LI>Next by Date: <STRONG><A HREF="msg00291.html">C&C and Event Rescheduling</A></STRONG> </LI> <LI>Prev by thread: <STRONG><A HREF="msg00282.html">Re: [MUD-Dev] Mail not getting to the list</A></STRONG> </LI> <LI>Next by thread: <STRONG><A HREF="msg00296.html">Re: [MUD-Dev] OT: Mail not getting to the list</A></STRONG> </LI> <LI>Index(es): <UL> <LI><A HREF="index.html#00290"><STRONG>Date</STRONG></A></LI> <LI><A HREF="thread.html#00290"><STRONG>Thread</STRONG></A></LI> </UL> </LI> </UL> <!--X-BotPNI-End--> <!--X-User-Footer--> <!--X-User-Footer-End--> <ul><li>Thread context: <BLOCKQUOTE><UL> <LI><STRONG>Re: [MUD-Dev] Graphic MUDS/Ultima Online</STRONG>, <EM>(continued)</EM> <ul compact> <ul compact> <LI><strong><A NAME="00606" HREF="msg00606.html">Re: [MUD-Dev] Graphic MUDS/Ultima Online</A></strong>, Jeff Kesselman <a href="mailto:jeffk#tenetwork,com">jeffk#tenetwork,com</a>, Fri 15 Aug 1997, 16:56 GMT </LI> </ul> </ul> </LI> <LI><strong><A NAME="00268" HREF="msg00268.html">Mail not getting to the list</A></strong>, coder <a href="mailto:coder#ibm,net">coder#ibm,net</a>, Tue 29 Jul 1997, 22:11 GMT <UL> <LI><strong><A NAME="00269" HREF="msg00269.html">Re: [MUD-Dev] Mail not getting to the list</A></strong>, Caliban Tiresias Darklock <a href="mailto:caliban#darklock,com">caliban#darklock,com</a>, Tue 29 Jul 1997, 22:52 GMT <UL> <LI><strong><A NAME="00282" HREF="msg00282.html">Re: [MUD-Dev] Mail not getting to the list</A></strong>, Jeff Kesselman <a href="mailto:jeffk#tenetwork,com">jeffk#tenetwork,com</a>, Wed 30 Jul 1997, 11:30 GMT <UL> <LI><strong><A NAME="00290" HREF="msg00290.html">Re: [MUD-Dev] OT: NIS/AlterNIC and the DNS system</A></strong>, Caliban Tiresias Darklock <a href="mailto:caliban#darklock,com">caliban#darklock,com</a>, Wed 30 Jul 1997, 22:26 GMT </LI> </UL> </LI> <LI><strong><A NAME="00296" HREF="msg00296.html">Re: [MUD-Dev] OT: Mail not getting to the list</A></strong>, clawrenc <a href="mailto:clawrenc#cup,hp.com">clawrenc#cup,hp.com</a>, Thu 31 Jul 1997, 06:00 GMT </LI> <LI><strong><A NAME="00297" HREF="msg00297.html">Re: [MUD-Dev] OT: Mail not getting to the list</A></strong>, clawrenc <a href="mailto:clawrenc#cup,hp.com">clawrenc#cup,hp.com</a>, Thu 31 Jul 1997, 06:07 GMT </LI> </UL> </LI> </UL> </LI> <LI><strong><A NAME="00265" HREF="msg00265.html">Re: [MUD-Dev] Graphic MUDS.</A></strong>, Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Tue 29 Jul 1997, 21:49 GMT <UL> <li><Possible follow-up(s)><br> <LI><strong><A NAME="00266" HREF="msg00266.html">Re: [MUD-Dev] Graphic MUDS.</A></strong>, Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Tue 29 Jul 1997, 21:49 GMT </LI> </UL> </LI> </UL></BLOCKQUOTE> </ul> <hr> <center> [ <a href="../">Other Periods</a> | <a href="../../">Other mailing lists</a> | <a href="/search.php3">Search</a> ] </center> <hr> </body> </html>