Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!sdd.hp.com!decwrl!hayes.fai.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: siegman@sierra.stanford.edu (siegman)
Newsgroups: comp.dcom.telecom
Subject: Re: A Thesis on Caller ID
Message-ID: <10812@accuvax.nwu.edu>
Date: 13 Aug 90 21:51:14 GMT
Sender: news@accuvax.nwu.edu
Organization: Stanford University
Lines: 20
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 10, Issue 566, Message 5 of 8


Jerry Leichter writes:

>In telephony terms, this means that I should have the right to send
>my ID or not; and you have the right to receive it, and refuse to
>answer if I didn't send it.

>A better Caller-ID system - though perhaps technically impractical
>- would be a button or setting on your phone that explicity asked
>for Caller-ID.  I would receive a notification of the request and 
>could choose to allow my identification to be sent, or not.  This
>would be the electronic analogue of your asking for my name -
>except that I would be unable to lie about it.

You've got it!  Exactly right!  The telco won't like it, the
prospective business users of Caller-ID will absolutely hate it, BUT I
WANT THAT BUTTON!  (NOT some special code I have to send each time,
NOT a special service I have to pay for, but _that button_, right
there on the phone for each and every call).  (And it's not
technically impractical at all either, is it?)