Return-Path: <tytso@thunk.org>
Received: from fort-point-station.mit.edu by po11.mit.edu (8.9.2/4.7) id BAA28186; Wed, 22 May 2002 01:32:08 -0400 (EDT)
Received: from thunk.org (THANK.THUNK.ORG [216.175.175.163])
	by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id BAA15000;
	Wed, 22 May 2002 01:31:21 -0400 (EDT)
Received: from think.thunk.org ([216.175.175.162])
	by thunk.org with asmtp (Exim 3.35 #1 (Debian))
	id 17AOiX-0002N0-00; Wed, 22 May 2002 01:31:21 -0400
Received: from tytso by think.thunk.org with local (Exim 3.35 #1 (Debian))
	id 17AOiW-0004n6-00; Wed, 22 May 2002 01:31:20 -0400
Date: Wed, 22 May 2002 01:31:20 -0400
From: "Theodore Ts'o" <tytso@MIT.EDU>
To: Angie Kelic <sly@mit.edu>
Cc: sipb-discussion@mit.edu, sipb-office@mit.edu
Subject: Re: SIPB role in advocacy sane network diagnostic advocacy
Message-ID: <20020522053120.GD12749@think.thunk.org>
References: <20020521184442.5B51F151EBE@industrial-algebra.mit.edu> <200205212015.QAA25490@prowler.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200205212015.QAA25490@prowler.mit.edu>
User-Agent: Mutt/1.3.28i

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
