Newsgroups: comp.mail.uucp
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!malgudi!osc.edu!karl.kleinpaste
From: karl.kleinpaste@osc.edu
Subject: Re: UUNET Problems
Message-ID: <1991Jun12.155958.15948@oar.net>
Sender: news@oar.net
Nntp-Posting-Host: ashley.osc.edu
Organization: Viento Gigabit Testbed, Ohio Supercomputer Center
References: <1991Jun11.143710.17578@tygra.Michigan.COM>
Date: Wed, 12 Jun 1991 16:57:49 GMT
Lines: 21

jp@tygra.Michigan.COM writes:
   Excuse me, but the problem would have to be the internal
   link between UUNET and CompuServe...

Naive conclusion.  That's no surprise, coming from you, Mr Palmer.

No, the problem would not have to be the UUNET/CompuServe link.  It
could be, but by no means has to be.  Rather, and more likely, the
problem is internal to CompuServe's own network, e.g., packet queueing
overruns between their own nodes.  Considering what their network is
built from, that's more than a little bit likely.

I could tell a horror story or three about local 9600bps access here
in Columbus with high packet latency due to travel through no less
than 7 CompuServe switching nodes before reaching the final host in
question.

Before making illogical leaps, consider the set of possibilities a
little more carefully, Mr Palmer.

--karl