Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!ucbcad!ucbvax!GVAX.CS.CORNELL.EDU!jqj
From: jqj@GVAX.CS.CORNELL.EDU.UUCP
Newsgroups: comp.protocols.tcp-ip
Subject: Re: ARPAnet congestion (was TN3270)
Message-ID: <8706041503.AA13470@gvax.cs.cornell.edu>
Date: Thu, 4-Jun-87 11:03:16 EDT
Article-I.D.: gvax.8706041503.AA13470
Posted: Thu Jun  4 11:03:16 1987
Date-Received: Sat, 6-Jun-87 07:33:50 EDT
References: <7408@cornell.UUCP>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: jqj@gvax.cs.cornell.edu (J Q Johnson)
Distribution: world
Organization: Cornell Univ. CS Dept, Ithaca NY
Lines: 7

One of the troubling things many of us learned last fall was that most of
the long distance Internet trunks are logical trunks leased from the various
phone companies without much regard to the physical path they take.  Has
any progress been made in determining the physical paths that the long distance
ARPAnet (and more importantly Milnet) links take?  Has progress been made in
insuring the survivability of Internet communications if a backhoe cuts
through a major AT&T fiber on the NY Thruway?