[27693] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Napster and others...

daemon@ATHENA.MIT.EDU (Erik E. Fair)
Thu Mar 9 13:33:40 2000

Mime-Version: 1.0
Message-Id: <v0422080ab4ed9bb6c397@[216.240.40.194]>
In-Reply-To: <00d501bf8912$844208c0$cfa728c3@knowledge.com>
Date: Thu, 9 Mar 2000 10:30:56 -0800
To: nanog@merit.edu
From: "Erik E. Fair" <fair@clock.org>
Cc: "Michael Ridley" <michael@napster.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Errors-To: owner-nanog-outgoing@merit.edu


Any operator trying to control which applications are used on their 
networks has either never learned, or already forgotten, the lesson 
of "fsp, NASA, and OZ."

Precis: they (developers, users) can modify the application to use 
spread-spectrum style port numbers that constantly change throughout 
the life of a session, which makes it effectively impossible to 
filter using existing technology.

Sean Doran has it right: be glad this is bulk TCP (fsp was UDP 
based), and turn on RED.

	Erik <fair@clock.org>


home help back first fref pref prev next nref lref last post