Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 alpha 4/15/85; site ucbvax.ARPA Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!tcp-ip From: tcp-ip@ucbvax.ARPA Newsgroups: fa.tcp-ip Subject: Re: MILNET/ARPANET performance Message-ID: <7563@ucbvax.ARPA> Date: Wed, 29-May-85 02:24:39 EDT Article-I.D.: ucbvax.7563 Posted: Wed May 29 02:24:39 1985 Date-Received: Thu, 30-May-85 04:06:39 EDT Sender: daemon@ucbvax.ARPA Organization: University of California at Berkeley Lines: 19 From: Mark Crispin There are those of us who are "homed" on both Milnet and ARPANET, and periodically need to telnet from hosts to a host on the other network, especially when software is being sloshed around all over the place. This isn't random hacking, either, this is real honest to goodness Internet business. It is NOT acceptable to tell us that the Milnet gateways are only for mail. It is NOT acceptable to tell us to use a TAC until such time as enough TAC dialups can be guaranteed. Of a number of Milnet TACs in this area, the only one with posted dialups is the SRI TAC, which has all lines busy about 50% of the time. I have local ARPANET host access, so I don't care much about local ARPANET TAC's, but I should note that as far as I know there aren't any public 1200 baud dialups on the local ARPANET TAC at Stanford (and I'm not aware of any others). -------