Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!rutgers!ucsd!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!bfmny0!tneff
From: tneff@bfmny0.UU.NET (Tom Neff)
Newsgroups: news.admin
Subject: Re: Disaster Planning
Keywords: doom naysayers death destruction
Message-ID: <14808@bfmny0.UU.NET>
Date: 26 Oct 89 23:11:03 GMT
References: <103@farcomp.UUCP> <35944@apple.Apple.COM> <14806@bfmny0.UU.NET> <362@cs.nps.navy.mil>
Reply-To: tneff@bfmny0.UU.NET (Tom Neff)
Distribution: news
Organization: ^
Lines: 24
Summary:
Expires:
Sender:
Followup-To:

I would think that posting to ebs.* would proceed under the assumption that
some or most of the affected area would be unable to receive it for a while.
But

 * the queueing and "flood" algorithm for news distribution ensures that
   when sites do come on line eventually they'll get it; this would be the
   first or only info they did get in this case.  As an admin I would
   find it most comforting.

 * setting up an alternate EBS "net" as defined in Sys files and so forth,
   could include vastly increased redundant connectivity (for ebs.* only)
   in the event of emergency.  For instance, I might have only five UUCP
   connections under normal conditions, but my backup EBS "sys" file might
   connect me to dozens of area machines to feed ebs.* only.  This maximizes
   the chance that a partially restored regional net would get vital stuff
   passed around.

 * Disruption of national connectivity could still leave well connected
   regional "pockets" which could then run on EBS.

These are just ideas to kick around.
-- 
Hey, where'd the Colombian Coffee ads go all of   %8  Tom Neff
a sudden!  Is Juan Valdez hiding in Panama?       8%  tneff@bfmny0.UU.NET