I'm not comfortable with this. It may be a technically valid 
interpretation, but I have a gut feeling that it will lead to 
inconsistent service. But I can't identify a specific case at the moment.

        Paul

Dean Willis wrote:
> 
> On Apr 14, 2008, at 11:19 PM, Paul Kyzivat wrote:
>>
>> It won't prevent calling the user with the name that looks like a 
>> number, at least not if a.com uses a location service. That is because 
>> the basic 3261 rules say to ignore the uri params when looking up in 
>> the location service.
>>
> 
> I disagree. Once you've decided to use an RFC 3261 location service, 
> what you say is probably correct. But the parameter can be used to make 
> an earlier decision to use telephony routing INSTEAD of using an RFC 
> 3261 location service.
> 
> RFC 3261 says:
> 
>> In addition to DNS and location service lookups shown in this example, 
>> proxy servers can make flexible "routing decisions" to decide where to 
>> send a request
> 
> So DNS is clearly a different sort of lookup than "location service". 
> ENUM is a DNS lookup, and I see no reason why "user=phone" is not a 
> valid flag for saying "don't do location service, do ENUM or TRIP or 
> other telephone routing instead".
> -- 
> Dean
> 
_______________________________________________
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