Hello Paul, Thanks a lot for your feedbacks and advice. I think I need to further investigate the solution before making any decision.
Thanks a lot for your time. Marc -----Message d'origine----- De : Paul Kyzivat [mailto:[EMAIL PROTECTED] Envoyé : mercredi 2 novembre 2005 15:32 À : VALENTIN M Ext ROSI/DPS Cc : [email protected] Objet : Re: [Sip-implementors] SIP: Use of Refer-To header Marc, You need to say more about what you intend. On the surface what you are describing sounds illegal. How do you intend to format Refer-To that is compatible with its syntax specification? IMO REFER is a very troublesome method. It looks like a single request with a bunch of options. But it doesn't say much about what the recipient should do. For example, when using REFER with the INVITE method, the recipient must do an INVITE. But there is explicit indication about how the recipient should manage its end of the invite - what media should be offered, how they should be connected to media handling resources in the UA, etc. The receiving UA must infer what it should do from context and knowledge of its own. The sender of the refer and the recipient must of course agree on what will happen for the results to be satisfactory. But none of that is standardized anywhere. Adding a new *unusual* usage of REFER just compounds that problem. Doesn't mean it shouldn't be done. But beware. Paul VALENTIN M Ext ROSI/DPS wrote: > Hi, > > I am about to specify the use of the REFER method in a way that differs from > its original purpose as specified in the RFC 3515. I am willing to use the > Refer-To header as a mean to bring particular information such as criteria. > That is to say the Refer-To header would not contain any SIP URI ou URL but > rather criterion identifier along with its value. > > Could you please tell if what I am intending to do is possible ? > > My concern is about knowing whether the UA receiving and accepting the REFER > is set on or forced to initiate a new dialog using the Refer-To information ? > Or can this UA only retrieve the information brought into the Refer-To header > without initiating any new dialog subsequently, for instance not specifying > any "method" parameter within the Refer-To header? If the case arises, could > you please advice me with the appended constrainsts ? > > Thanks a lot for you help > Marc > > > *********************************** > Ce message et toutes les pieces jointes (ci-apres le "message") sont > confidentiels et etablis a l'intention exclusive de > ses destinataires. > Toute utilisation ou diffusion non autorisee est interdite. > Tout message electronique est susceptible d'alteration. Le Groupe France > Telecom decline toute responsabilite au titre de > ce message s'il a ete altere, deforme ou falsifie. > Si vous n'etes pas destinataire de ce message, merci de le detruire > immediatement et d'avertir l'expediteur. > *********************************** > This message and any attachments (the "message") are confidential and > intended solely for the addressees. Any unauthorised > use or dissemination is prohibited. > Messages are susceptible to alteration. France Telecom Group shall not be > liable for the message if altered, changed or > falsified. > If you are not receiver of this message, please cancel it immediately and > inform the sender. > *********************************** > > _______________________________________________ > Sip-implementors mailing list > [email protected] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > *********************************** Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. Le Groupe France Telecom decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas destinataire de ce message, merci de le detruire immediatement et d'avertir l'expediteur. *********************************** This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. France Telecom Group shall not be liable for the message if altered, changed or falsified. If you are not receiver of this message, please cancel it immediately and inform the sender. *********************************** _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
