Path: utzoo!attcan!uunet!lll-winken!xanth!ukma!tut.cis.ohio-state.edu!monster.cis.ohio-state.edu!bob From: bob@monster.cis.ohio-state.edu (Bob Sutterfield) Newsgroups: news.misc Subject: Re: Cayman on the net Message-ID: Date: 22 May 89 05:05:21 GMT References: <2877@cayman.COM> <7345@hoptoad.uucp> <2895@cayman.COM> <7382@hoptoad.uucp> Sender: news@tut.cis.ohio-state.edu Reply-To: Bob Sutterfield Followup-To: news.misc Organization: The Ohio State University Dept of Computer & Information Science Lines: 21 In-reply-to: tim@hoptoad.uucp's message of 20 May 89 19:29:33 GMT If a company wants to provide mail access to itself, it should become a UUNET subscriber so that they are paying the bill for the largest flow choke point. If it wants to provide absolutely secure, absolutely reliable mail access to itself (as "absolutely" as you can get :-), and to throw in file transfers for maintenance and updates as well, it should set up direct UUCP links with its customers. We've done this with a vendor because they needed to be able to get kernel cores from our system and give us new kernel object modules, by dialing us from California. It was very useful. If a vendor wants to provide an electronic customer support forum, they should get themselves (and their customers) a "biz.all" feed and establish their own newsgroup there. That's why the "biz" distribution arose. Again, if they want to be as assured as possible that the flow of biz.all news is reliable, they should establish a direct feed with each customer for just this distribution (or perhaps even just their own group in that distribution). It's anarchistic capitalism at its best: You want it, you pay for it.