Re: Clarification on RFC 4458: SIP URIs for Applications suchas Voicemail and Interactive Voice Response (IVR)

<[email protected]>
Newsgroups gmane.ietf.sip
Message-ID <7DBAFEC6A76F3E42817DF1EBE64CB026065E70D3@ftrdmel2>
Hi, 

It is certainly true for those parameters in the R-URI but in the History-Info header it is less obivous because if RFC4244 is respected, the retargeting is yet present in a hi-entry (the proof is that the target parameter has not been especially recommended to be used in 3GPP for CDIV service). The benefit to add the target parameter in the R-URI in the hi-entry is to have in the same hi-entry the redirecting user and the cause-param. So that we can be sure of the redirecting user identity (which could be in an other hi-entry than the one "just before"). But after that, it is still necessary to search in hi-entries the entry concerning the redirecting address to have the Privacy indication (eg. to deliver or not the redireting user identity to the diverted-to user) and to know if the retargeting is caused by a SIP response or not (if the Reason header is escaped).

Regards,
Marianne

-----Message d'origine-----
De : [email protected] [mailto:[email protected]] De la part de Francois Audet
Envoyé : mercredi 8 avril 2009 18:10
À : DRAGE, Keith (Keith); [email protected]
Cc : Cullen Jennings; Elwell,John
Objet : Re: [Sip] Clarification on RFC 4458: SIP URIs for Applications suchas Voicemail and Interactive Voice Response (IVR)

I believe the intention was that target was mandatory, but not cause.

I don't believe having cause but not target would make any sense. 

> -----Original Message-----
> From: DRAGE, Keith (Keith) [mailto:[email protected]]
> Sent: Wednesday, April 08, 2009 09:07
> To: [email protected]
> Cc: Cullen Jennings; Audet, Francois (SC100:3055); Elwell, John
> Subject: Clarification on RFC 4458: SIP URIs for Applications such as 
> Voicemail and Interactive Voice Response (IVR)
> 
> RFC 4458 defines two SIP URI parameters.
> 
> I can find no specific language in the document that indicates whether 
> these two URI parameters can be used independently of each other, or 
> whether there is an expectation that both URI parameters should only 
> exist in the presence of each other. Specifically does an 
> implementation that only includes the "cause" SIP URI parameter and 
> not the "target" sip URI parameter conform to this specification?
> 
> All the text and examples seem to carry the implication that where one 
> exists, the other one will also.
> 
> Could one of the authors or some other interested party clarify what 
> they believe the intention is?
> 
> regards
> 
> Keith
> 
_______________________________________________
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
_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.