Return-Path: <TMcNerney@chipwrights.com>
Received: from fort-point-station.mit.edu by po11.mit.edu (8.9.2/4.7) id LAA19029; Fri, 21 Sep 2001 11:01:10 -0400 (EDT)
Received: from intranet.chipwrights.com (ipn2-a1131.net-resource.net [216.204.61.131])
	by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id LAA23246
	for <sipb@mit.edu>; Fri, 21 Sep 2001 11:01:07 -0400 (EDT)
Received: by intranet with Internet Mail Service (5.5.2650.21)
	id <SVQAX32S>; Fri, 21 Sep 2001 11:01:47 -0400
Message-ID: <93A4BBB9515ED411AE9D00508BD955A5198C1A@intranet>
From: "McNerney, Tim" <TMcNerney@chipwrights.com>
To: "'sipb@mit.edu'" <sipb@mit.edu>
Subject: Who do I talk to about e19-rtr-backbone.mit.edu lossage?
Date: Fri, 21 Sep 2001 11:01:37 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"

Hi,

I am looking for advice and maybe some advocacy.

I am an alum who has been in and around MIT
since the Multics days.  Over the last couple of years
I have been finding it harder and harder to ssh into
MIT to read my email and do other low-bandwidth
unix shell activities.  Recently it has become nearly im-
possible to keep a telnet connection up for more than a few
minutes.  Using "mtr" I see that e19-rtr-backbone.mit.edu
is dropping -lots- of packets on the floor.

What is the best forum for, not just venting my frustration,
but for getting some improvements?

Are Jeff Shiller and company doing anything about this?
(Is he even around anymore?)

Here's an idea:

Maybe the time is right for some sort of low-bandwidth, low-
latency path into MIT (without using dialups).  Is this something 
SIPB might be interested in helping with?

--Tim McNerney, AR'00


