1996-03-11 - Re: FCC & Internet phones

Header Data

From: Adam Shostack <adam@lighthouse.homeport.org>
To: wlkngowl@unix.asb.com (Mutant Rob)
Message Hash: 8e49dc988fcb26c2c6e69fdea2d3ec5f04fa7eadfb97fbdebbef3f8d42a9f58d
Message ID: <199603100507.AAA02942@homeport.org>
Reply To: <199603100222.VAA06105@bb.hks.net>
UTC Datetime: 1996-03-11 00:05:58 UTC
Raw Date: Mon, 11 Mar 1996 08:05:58 +0800

Raw message

From: Adam Shostack <adam@lighthouse.homeport.org>
Date: Mon, 11 Mar 1996 08:05:58 +0800
To: wlkngowl@unix.asb.com (Mutant Rob)
Subject: Re: FCC & Internet phones
In-Reply-To: <199603100222.VAA06105@bb.hks.net>
Message-ID: <199603100507.AAA02942@homeport.org>
MIME-Version: 1.0
Content-Type: text

Mutant Rob wrote:
| >         Q: Is it practically possible to find netphone traffic on a
| > generic network at any level above the source and target addresses?
| Good question.

Presumably, the signal has a number of charictaristics.  Some of them
have a central switchboard, where preople go to set up calls.  Most
presumably use a mix of a UDP data connection and tcp for control
functions.  They all consist of high volume, long duration connections
(or data flows in the case of UDP.)  Many probably use a standardized
destination port.  They might use the urgent pointer to force data up
the stack quickly.

	In short, yes the data streams can be easily found, if one can
tap and grep a T3 in real time.


"It is seldom that liberty of any kind is lost all at once."