1996-08-15 - Re: (Off Topic) Re: FCC_ups

Header Data

From: Bill Stewart <stewarts@ix.netcom.com>
To: cypherpunks@toad.com
Message Hash: d102bfe571f1a144468878e46e6f5577517abadf0678cde9d83b80234573bc9e
Message ID: <199608142306.QAA07654@toad.com>
Reply To: N/A
UTC Datetime: 1996-08-15 01:52:04 UTC
Raw Date: Thu, 15 Aug 1996 09:52:04 +0800

Raw message

From: Bill Stewart <stewarts@ix.netcom.com>
Date: Thu, 15 Aug 1996 09:52:04 +0800
To: cypherpunks@toad.com
Subject: Re: (Off Topic) Re: FCC_ups
Message-ID: <199608142306.QAA07654@toad.com>
MIME-Version: 1.0
Content-Type: text/plain


At 10:45 AM 8/13/96 -0700, shamrock@netcom.com (Lucky Green) wrote:
>>The *real* challenge: how do you support sender- and recipient- anonymous
>>phone calls with strong security?  Have fun.
>
>Sender anonymous phone calls are easy. You route them through PipeNet,
>assuming every PipeNet node has a telephony gateway. Recipient anonymous
>phone calls a harder to implement.

Assuming PipeNet is a descendant of the Packet Laundry concept,
recipient-anonymous phone calls are also easy - build a meet-me box,
AKA conference bridge.  Recipient John Doe #3 reserves a conference bridge,
sends anon-email to John Doe #6 and John Doe #43, saying "meet me at
Bridge7.conference.netphone.com at midnight Zulu time, password 'foobar'"
and they all call in.  

Payment: If the conference bridge is run by a vanilla commercial
Internet-telephony service, it may want some sort of non-private payment, 
but would probably accept phone cards.  Otherwise you're stuck with credit
cards.

If it's run by an enlightened service provider or some sort of punknet,
it'll take anonymous digicash.  Maybe the host pays, maybe everybody.
Or you could digitally record the sounds of dropping quarters in a payphone :-)

#			Thanks;  Bill
# Bill Stewart, +1-415-442-2215 stewarts@ix.netcom.com
# <A HREF="http://idiom.com/~wcs"> 	Defuse Authority!






Thread