🚀 go-pugleaf

In article <slrn5ls7gl.b1c.jerobins@pong.cc.ncsu.edu>,
jerobins@unity.ncsu.edu wrote:

> I do believe you fail to recall the numerous problems with the MCI link
> to Atlanta.  So bad that MCI moved the link from Atlanta to
> Greensboro....at least our link to DC via Sprint has been reasonably
> stable as compared to MCI, if only we could get a packet *though* DC,
> now that would be cool.
>   James

Considering that there is very little between us and DC, the "reliability"
of Sprintnet locally is next to useless.  MCI was certainly not without its
faults, but we never ever had these consistent, daily, nonstop problems, as
documented by our own Duke-originated pings & traceroutes as well as
measurements from other locations such as www.netstat.net or
www.internetweather.com.

In the prelapsarian days of MCI, I didn't mind realistic, occasional
problems indicative of Internet-wide saturation, especially when they are
fixed relatively quickly.  What I can't stand now is suffering 20-100%
packet losses lasting for hours nearly every day, with a baseline loss
level between 10-20% even during the best of times, compounded by
horrendous routing.  There is NO question that the MCI to Sprintnet switch
resulted in a drop of quality to a level well below what we need.

Joseph Lo, Ph.D.
Dept. of Radiology

-- 
To email me, please delete the "NO_SPAM" from my address, thanks.