Re: francois' comments and why RFC4474 not used in the field

Jonathan Rosenberg wrote:
> inline:
> 
> Jiri Kuthan wrote:
> 
> 
>>>  From an end user perspective, I would assert that the most important 
>>> thing is probably the media. If the callerID says, "this is bob", 
>>> what is important to the user, is that when I pick up the phone and 
>>> start talking, it will be Bob who hears me, and Bob that I hear.
>>>
>>> Consider this litmus test:
>>>
>>> If the signaling actually came from Mary (perhaps as a third party), 
>>> but the media goes/comes to/from Bob, who should appear on the caller 
>>> ID? I say - Bob.
>>
>> There is a timing aspect in favor of placing identity in signaling --
>> I would like to know whose call is ringing before I answer (if I do).
> 
> You can still have that. Just don't ring the phone until early media has 
> been exchanged and verified. Indeed if you were doing an ICE-style thing 
> per Dan's draft, you'd get that for free.

Hi Jonathan,

Ok, that's feasible in a sense. And there is certain beauty in getting the
security attributes associated with RTP packets, to which they belong.
(I like this about zRTP). A particular example where this would perform
well is today's PSTN directory service, which connects me to the final
recipient, while still the directory's service phone number appears on
my phone. (well, with connected identity one could actually handle
it using signaling too...)

What I'm anxious of is the idea of to do "x" you also have to do
"y" which you need for "z" anyhow -- doesn't that impair the feasibility?
Could not we find something that is just as easy as to do "x" do "x"?


-jiri
_______________________________________________
Sip mailing list  https://www.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