Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/15/85; site gould9.UUCP
Path: utzoo!watmath!clyde!cbosgd!gould9!joel
From: joel@gould9.UUCP (Joel West)
Newsgroups: net.news
Subject: Gatewaying mod.* from ARPA lists
Message-ID: <201@gould9.UUCP>
Date: Tue, 10-Dec-85 11:14:50 EST
Article-I.D.: gould9.201
Posted: Tue Dec 10 11:14:50 1985
Date-Received: Wed, 11-Dec-85 04:22:11 EST
References: <344@brl-tgr.ARPA>
Distribution: net
Organization: CACI, Inc. -- La Jolla, Calif.
Lines: 23
Summary: add Article-ID at source

This is something I've been thinking about for a while.

If we could get the maintainers of the ARPA digests to add their own 
Article-ID when they create the digest, then we could have multiple 
gateways to Usenet and improve propagation and reliability.

That is to say, may UUCP and ARPA/UUCP sites are already on these mailing 
lists -- the articles come in, usually to a local redistribution list.

If, at that time, a few sites (rather than 1) could inject the article
into the net, we wouldn't have all the problems about lost mod.*
articles (we'd have new ones.... :-) 

The only impediment to this, it seems to me, is that we want the
Article-ID established at the origin site (as with "genuine" usenet
mod. groups) so that the duplicates are detected and not-redistributed.

I'll volunteer to add mod.computers.{mac,ibmpc} here.
-- 
	Joel West	 	(619) 457-9681
	CACI, Inc. Federal, 3344 N. Torrey Pines Ct., La Jolla, CA  92037
	{cbosgd,ihnp4,pyramid,sdcsvax,ucla-cs}!gould9!joel
	gould9!joel@nosc.ARPA