Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!zaphod.mps.ohio-state.edu!sdd.hp.com!decwrl!shelby!morrow.stanford.edu!Valinor.Stanford.EDU!vaf
From: vaf@Valinor.Stanford.EDU (Vince Fuller)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Serious Routing Problems
Message-ID: <1990Aug10.014609.2806@morrow.stanford.edu>
Date: 10 Aug 90 01:46:09 GMT
References: <61620@bu.edu.bu.edu> <9007311833.AA22548@nsipo.arc.nasa.gov>
Sender: news@morrow.stanford.edu (USENET News System)
Reply-To: vaf@Valinor.Stanford.EDU (Vince Fuller)
Organization: Data Center, Stanford University, California, USA
Lines: 20

-----

Kent,
  To follow-up on Milo's comments about routing protocols - BARRNet has been
running OSPF for several months now and we are pleased with it for a variety
of reasons, one of which being its ability to quickly re-route around failures.
When a line flap occurs somewhere in the system, the OSPF part of
BARRNet recovers quickly and things stabilize within a matter of
seconds. Unfortunately,
the non-OSPF part of BARRNet is not so fortunate - the non-SPF protocols
that it
runs immediately go into hold-down when a line flap occurs, partitioning the
network for the duration of the hold-down period (several minutes). We
find this 
very annoying and is one of the (many) reasons that we have been pushing
so hard
for widespread implementation of OSPF.

	Vince Fuller, BARRNet technical coordinator
	(BARRNet is an equal-opportunity vendor basher)