Subject: Re: [Sipping] Clearing the pipeline in re service identification

From: "Andrew Allen" <[email-masked]>
Date: Thu, 22 Mar 2007 05:22:44 -0400

This is just a preloaded Route like any other. If I put an invalid URI in a Route header then it fails regardless of whether its a URN or some other URI.

--------------------------
Andrew Allen
Manager Standards
Research In Motion Ltd
BlackBerry Mobile  +1 847 809 8636
http://www.rim.com/

Sent from my BlackBerry Wireless Handheld

----- Original Message -----
From: Paul Kyzivat <[email-masked]>
To: [email-masked] <[email-masked]>
Cc: [email-masked] <[email-masked]>
Sent: Thu Mar 22 05:05:46 2007
Subject: Re: [Sipping] Clearing the pipeline in re service identification

[email-masked] wrote:

>    From: Paul Kyzivat <[email-masked]>
> 
>    I don't see the issue with this. If I just use a URN as a URI in a Route 
>    header, either it will succeed or it will fail. If I put it in as a 
>    strict route then the proxy I forward it to will be the one that must do 
>    it or fail. If I put it in as a loose route then it is only necessary 
>    that it *eventually* get to a proxy that can figure it out.
> 
> Yeah, but that assumes that every proxy before that has *some* strategy
> for dealing with the service URN, presumably by forwarding it "toward
> the center", hoping that a studlier proxy will be able to understand
> the request.
> 
> But it's fairly safe to assume that in practice, unless a proxy was
> explicitly coded to implement the service-URN-Route, it will discover
> that it can't understand the Route and will reject (or just drop) the
> request.

Sure it can fail. But it doesn't need a Proxy-Require to make it fail. 
Presumably you wouldn't include such a route into your request unless 
you had reason to suspect it would work. If you need this to make some 
service work, and it fails, then you just can't use that service.

	Paul

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [email-masked] for questions on current sip
Use [email-masked] for new developments of core SIP

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [email-masked] for questions on current sip
Use [email-masked] for new developments of core SIP