Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!think!ames!sdcsvax!ucbvax!NOTE.NSF.GOV!steve
From: steve@NOTE.NSF.GOV
Newsgroups: comp.protocols.tcp-ip
Subject: Re: User chargeback issues
Message-ID: <8709151611.aa27463@note.nsf.gov>
Date: Tue, 15-Sep-87 18:05:04 EDT
Article-I.D.: note.8709151611.aa27463
Posted: Tue Sep 15 18:05:04 1987
Date-Received: Thu, 17-Sep-87 06:30:20 EDT
References: <8709151005.aa29600@SMOKE.BRL.ARPA>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 15


     3.  The final gotcha is that user chargeback needs to be implemented
     in a way that doesn't open the door to traffic analysis.  
     Even if we don't chargeback to users, the data flow info is useful --
     to Ivan as well as the network managers.  I've been in law
     enforcement long enough to know how valuble telephone tolls are
     in tracking a smuggler and his activities -- let's not set ourselves
     up.

Get real.  The door is already open to traffic analysis, and if (110 dB rattle
of saber) "Ivan" really cares, he's already doing it.

Chargeback is a totally orthogonal issue.

-s