Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!ctrsol!lll-winken!arisia!sgi!shinobu!odin!zamna.sgi.com!wicinski From: wicinski@zamna.sgi.com Newsgroups: comp.protocols.tcp-ip Subject: Re: New Host-Requirement RFCs Message-ID: <1156@odin.SGI.COM> Date: 29 Oct 89 07:41:33 GMT References: <8910201839.AA29376@arcturus.mitre.org> <1136@odin.SGI.COM> Sender: news@odin.SGI.COM Reply-To: wicinski@zamna.sgi.com () Organization: Silicon Graphics, Inc., Mountain View, CA Lines: 40 >rick@uunet.UU.NET (Rick Adams) says: Did he listen to what i said - NO. I stated: getting registered is NOT easy. The forms are confusing The instrustions are opaque Everything is geared for people who are directly connected. }>No. The $35 is to pay for the hassle involved with reading and correcting the }>forms (30% arrive with errors in them) and for RUNNING THE NAMESERVERS. }> }>Frankly the $35 one time fee doesn't cover the time and effort involved. What a MINUTE - Don't you think something might be WRONG if 30% of them come back with ERRORS? perhaps what i said could be true - ie, the instructions were not written for the people who are filling them out. When i see an error rate of 30 percent i have to say "WHOA, something is wrong with the paradigm." Is everyone committing the same error - perhaps then something should be done to clarify the process. And maybe if you do that, the error rate will drop and you can you time more relevant tasks. The problem boils down to this: When you are directly connected to the Internet, registering is easy. The forms are simple, quick, and direct (i know, I've filled them out this way). When you are not directly connected to the Internet the forms are really a hassle. Most of it becomes non relevant. The problem is the NIC hasn't quite caught on to the fact that more and more domains are non-connecting. Another problem with forwarders and going around begging for one is how it can/will turn into a subtle form of censorinship, turning domain server masters into net nazis for the sake of making sure there systmes are "pure" (and if you don't believe me, i can pull TWO cases out of my mail archives where i received notes from systems nerds stating the content of the flow of mail through their system was "inappropriate behavior for their machines to handle", and in both cases it was caused by pathalias totally botching my direct *source routes*... and peoplewonder why i crypt all my mail...). tim