Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!ucbcad!ucbvax!UDEL.EDU!Mills
From: Mills@UDEL.EDU
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  On broadcasts, congestion and gong
Message-ID: <8710272128.aa11618@Huey.UDEL.EDU>
Date: Tue, 27-Oct-87 21:28:13 EST
Article-I.D.: Huey.8710272128.aa11618
Posted: Tue Oct 27 21:28:13 1987
Date-Received: Sat, 31-Oct-87 00:43:28 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 18

Mike,

Your scenario about unrecognized broadcast packets and sneak paths via
default gateways is exactly what happened in the recent case where
net 128.220 RIP packets crashed and burned at linkabit-gw. Fortunately,
the RIP packets did not survive the airspace to NSNET client networks,
where the collateral damage might have been spectacular.

The recent turbulence when net 0.0.0.0 was accidently sqwawked to the
corespeakers and evidently was squawked right back to the Kirton
code on one or more systems seems to confirm your suspicion that
a "default" sneaked via EGP can run amok on the local net. This should
be fixed.

My comment about RFC-1009 compliance was also intended for you. Can
you remark on the compliance of 4.3, lack of it or reasons wherefore?

Dave