Pars Mutaf wrote:
On 10/9/07, *Joel M. Halpern* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
At 08:58 AM 10/9/2007, you wrote:
>Where did you get this information. It is private.
Presumably, the "this" refers to the SIP URI.
If you don't have the SIP URI, what string do you think you
have? Human names are utterly useless for this, due to collision,
misspelling, and many other problems.
To my knowledge, phonebook users never complained about that.
Phone books worked reasonably well in a different age. And they depended
on people being willing to advertise certain context information to the
public at large: their phone number and an address. I think today that
people are not so willing to disclose that information publicly.
Today we often want to talk to people whose addresses we often don't
know. Instead we may know their email address, or an IM address, etc.
And those things are at least unique.
So there are two problems here:
- trying to find a unique address for someone given only
some human name you have for them, and to disambiguate
them from all the other people with similar names based
on whatever information they might be willing to disclose
to a random stranger.
- given some unique address that is known to be associated
with a given individual, find a different address for the
same individual that is usable for some desired form of
communication.
The latter is probably a much more solvable problem.
The real problem of the phonebook, today, is the privacy
problem. An extension is needed for interactive user
permissions as stated by Adam Roach.
A note about name collisions:
Similarly to a traditional phonebook user, if you are looking
for a certain John Smith, hopefully you will have some
additional information helping filter the results.
(in the proposed extension, the target cell phone may return
such information, e.g. company name, street address, etc.)
I'm not likely to have my phone return that sort of information to
unknown requestors. I don't know who would.
Note also that if anyone can send you a resolution request, that is
roughly equivalent, in terms of intrusiveness, to anyone causing your
phone to ring.
The proposal is rather as follows (abstract):
You solve to a challenge (e.g. a CAPTCHA) to obtain the target
phone number.
Then, you can make a call, send a message etc.
Really! Maybe you are willing to give your information out to anyone who
can solve a CAPTCHA, but I'm not.
Note that in Adam's example you might be sending this request to dozens,
hundreds, or more of targets that you are not interested in, and who are
presumably not interested in you either. Then you are going to solve a
capcha from each one enroute to finding the right one? And they are
going to go along with this?
Paul
Thanks,
pars
Alternatively, if you want a challenge / response on the resolution
request, you can give a challenge / response on the SIP request.
Yours,
Joel
------------------------------------------------------------------------
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
