Subject: RE: [Sip] Re: Use of SIP and SIPS URIs in Refer-to header

From: "Francois Audet" <[email-masked]>
Date: Wed, 21 Sep 2005 19:36:35 -0500

Presumably, another REFER could then be sent with Refer-to
sip, provided it conforms to the policy, right?

> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]] On 
> Behalf Of Robert Sparks
> Sent: Wednesday, September 21, 2005 16:25
> To: Elwell John
> Cc: [email-masked]; [email-masked]
> Subject: [Sip] Re: Use of SIP and SIPS URIs in Refer-to header
> 
> 
> inline
> On Sep 21, 2005, at 11:13 AM, Elwell John wrote:
> 
> > Robert,
> >
> > I have been unable to find any guidance on the use of SIP and SIPS
> > URIs in the Refer-to header in either the REFER RFC or the cc- 
> > transfer draft. Suppose the UAC for a REFER request places a SIPS  
> > URI in the Refer-to header and that the UAS does not support TLS.  
> > In this case the UAS for the REFER request would be unable 
> to issue  
> > the required SIPS request. Should it send a NOTIFY with response  
> > code 404, or should it make the referred request using the SIP URI  
> > scheme? If the former, is it reasonable to repeat the REFER 
> request  
> > with a SIP URI in the Refer-to header?
> >
> > John
> >
> The REFER recipient would reject the REFER in this case. Same 
> as if the URI was to an http: URI and the receiving agent 
> didn't know what to do with those.
> 
> RjS
> 

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