Return-Path: <kenta@MIT.EDU>
Received: from grand-central-station.mit.edu by po11.mit.edu (8.9.2/4.7) id DAA28112; Wed, 22 May 2002 03:45:04 -0400 (EDT)
Received: from manawatu-mail-centre.mit.edu (MANAWATU-MAIL-CENTRE.MIT.EDU [18.7.7.71])
	by grand-central-station.mit.edu (8.9.2/8.9.2) with ESMTP id DAA22396;
	Wed, 22 May 2002 03:44:21 -0400 (EDT)
Received: from magic-pi-ball.mit.edu (MAGIC-PI-BALL.MIT.EDU [18.7.16.80])
	by manawatu-mail-centre.mit.edu (8.9.2/8.9.2) with ESMTP id DAA21227;
	Wed, 22 May 2002 03:44:21 -0400 (EDT)
Received: from localhost (kenta@localhost) by magic-pi-ball.mit.edu (8.9.3) with ESMTP
	id DAA27289; Wed, 22 May 2002 03:44:21 -0400 (EDT)
Date: Wed, 22 May 2002 03:44:21 -0400 (EDT)
From: Ken T Takusagawa <kenta@MIT.EDU>
To: <sipb-discussion@mit.edu>, <sipb-office@mit.edu>
Subject: Re: SIPB role in advocacy sane network diagnostic advocacy
In-Reply-To: <20020522053120.GD12749@think.thunk.org>
Message-ID: <Pine.GSO.4.30L.0205220335310.26873-100000@magic-pi-ball.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Perhaps someone can write a packet-sniffer that prints out
only the origin of packets and nothing else.  Certainly this
is less privacy-violating than running `top` or `ps` on the
dialups.

Then we try to get this program "blessed" by networkological
administrators: use of this specific program unmodified does
not constitute a violation of rules of use.

--ken (new prospective)



On Wed, 22 May 2002, Theodore Ts'o wrote:

> On Tue, May 21, 2002 at 04:15:46PM -0400, Angie Kelic wrote:
> > I am going to clarify this.
> >
> > 1) we are gearing up to deploy our own network monitoring tools in
> > the dorms
> >
> > 2) sniffing of traffic not intended for you is indeed against the
> > rules of use and is frowned upon
> >
> > 3) the CoD is in fact where people do get brought up for repeated
> > violations of the rules of use or aggregious network violations
>
> At least in the past, there was a significant difference between
> sniffing the contents of network communication (in fact that's what
> traffic means in many contents).  Certainly the specific rule of use
> in question, "don't violate the privacy of other users" is such that
> it's not entirely clear that seeing who is consuming an unfair amount
> of a shared resource, without actually looking at what is being
> transmitted, is actually "violating the privacy of other users".
>
> To the extent that there is a significant problem in terms of
> networking in the dormitories, cracking down on those people who are
> trying to make the best of a bad situation (especially when said
> crackdown seems to be based on a very narrow, bureaucratic,
> tomatoes-and-lettuce style reading of the rules of use) seems to be
> counterproductive, and gives the network group a reputation of one
> which isn't interested in trying to solve the problem.  I'm aware this
> reputation is not fair, but this stand tends perpetuate this
> reputation.
>
> I don't think there's any denying the fact that (1) there's a problem,
> (2) the problem has been going on for a long time, and (3) one of
> SIPB's role as an advocate for computing on campus is to try to
> encourage solutions.
>
> OK, fine, it's too hard to put in switches instead of hubs in the
> dorms, for various reasons, both technical and political.  But if the
> RCC's don't like volunteers trying to find people who are overloading
> the network, it'd be nice to know that *someone* is going to do this
> --- and if so, why not allow volunteers to help find machines which
> are overloading dorm networks, just as I/S uses volunteers to find
> security problems?
>
> Or is the official policy that people who are flooding the network and
> causing problems for other users should be allowed to continue doing
> that, while people who are trying to find the problem users are
> stomped upon?
>
> It just doesn't seem reasonable.
>
> 						- Ted
>


