I'll reiterate my key point here at the top: we cannot retroactively 
change the behavior of deployed user agents. All we can do is make sure 
what we're proposing doesn't make do stupid and/or useless things.

More inline.

On 3/13/08 6:26 PM, Dean Willis wrote:
>
> On Mar 13, 2008, at 1:58 PM, Adam Roach wrote:
>
>> On 3/13/08 11:59 AM, Dean Willis wrote:
>>> We could fix this by having gateways encode their identity using a  
>>> reserved userpart. This has to have the  property of saying "Do not  
>>> display this as caller-ID". Using "sip:domain" or "sip:ipaddress" 
>>> does  not work, as those might actually be valid URIs that be be 
>>> displayed  as IDs.
>>>
>>
>> That's the problem I have -- if the calling party reported by the 
>> PSTN has been completely pulled out of the "From" header field, then 
>> you'll have very bad interaction with currently deployed phones. I 
>> don't think that's a reasonable trade-off. That's why I think this...
>
> That;s why John proposed P-AI-ID as the Caller-ID source.


The phone on my desk would treat that like any other unknown header, and 
ignore it.

>
>>
>>
>>> It might work to have the gateway use a reserved value, like 
>>> "sip:[EMAIL PROTECTED]".
>>>
>>
>> ...is a non-starter.
>
> How about:
>     From: +12142821376 <sip:[EMAIL PROTECTED]>
>


If I missed that call, the phone on my desk would helpfully offer to 
call "sip:[EMAIL PROTECTED]" when I got back. I don't think I'll be 
happy with the results.


>> That would argue for some indication on the *From* header field that 
>> indicates a level of trust. I'm not sure it's really the proper place 
>> to place that information, from a semantic perspective -- but it does 
>> seem to be a potential way to get through this maze of thorns without 
>> losing too much blood.
>
> I like it.

Okay, we might be getting somewhere then. Anyone else?

/a
_______________________________________________
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

Reply via email to