Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-lcc!ames!ucbcad!ucbvax!CITHEX.CALTECH.EDU!carl
From: carl@CITHEX.CALTECH.EDU
Newsgroups: mod.computers.vax
Subject: Re(2) E-MAIL Blackouts
Message-ID: <870315054052.04j@CitHex.Caltech.Edu>
Date: Sun, 15-Mar-87 08:40:50 EST
Article-I.D.: CitHex.870315054052.04j
Posted: Sun Mar 15 08:40:50 1987
Date-Received: Mon, 16-Mar-87 04:07:29 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 13
Approved: info-vax@sri-kl.arpa

You're definitely right: optimally, ALL teleconferences should be set up
heirarchically to the fullest extent possible.  Here at CALTECH, we've got
one machine which handles (in theory) all incoming teleconference traffic,
keeping a copy for itself, and forwarding copies to other machines on campus;
these machines in turn redistribute teleconferences to individual users or
machines not accessible to the central machine.  On most VMS systems here, the
teleconferences are not distributed to individual users, but a single copy of
the messages is maintained in a format that allows the users to read it.
If anybody out there is managing a teleconference that is sending stuff to
any machine other than CALTECH (or HAMLET) in the .CALTECH.EDU domain, please
get in touch with me (or KEN@HAMLET) so that appropriate routing can be set up.
By the way, there DO exist gateways between EARN and ARPA that don't involve
WISCVM, but I decline to go into specifics.