Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-crg!ames!ucbcad!ucbvax!A.ISI.EDU!LYNCH From: LYNCH@A.ISI.EDU (Dan Lynch) Newsgroups: mod.protocols.tcp-ip Subject: Re: Arpanet outage Message-ID: <8612171035.AA12093@ucbvax.Berkeley.EDU> Date: Tue, 16-Dec-86 21:00:01 EST Article-I.D.: ucbvax.8612171035.AA12093 Posted: Tue Dec 16 21:00:01 1986 Date-Received: Thu, 18-Dec-86 00:27:10 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 22 Approved: tcp-ip@sri-nic.arpa Ken (and the others who have jumped into this), Wow. I guess this surfaced an issue that many of us had taken for granted -- that those who are responsible for deploying the Arpanet and Milnet (and who know what else) have been keeping the "diversity of routing" high enough to ensure "reliability/survivability" of data links during even normal times. (There wil always be a farmer in Illinois who digs before asking.) Anyway, here's hoping we can benefit from this recent minor debacle. One additional query of those in the know: when the service was restored did things just start to work again or did some manual intervention get packets routing on their merry way? Dan PS. I really like to have these "system level" discussions whenever we are "lucky" enough to have serious disruptions of the underlying technology. Thye are rare events and we think we have designed our methods to deal with them. And we rarely have the guts to blast ourselves out of the water to "test" them. -------