El Martes, 1 de Diciembre de 2009, Paul Kyzivat escribió: > > Yes, but that makes sense when setting the URI as Request URI and so, but > > I just mean the URI with identifies a user, this is, the same URI that > > the user sets in "From" header or credentials "username" field. > > The cases where such things will show up in From are fewer than those > where it might show up in To. > > There is the case where you had called me, and used a gruu for your > Contact address. Later I use that contact to establish a separate dialog > to you, and so I use it as both the R-URI and the To-URI. Subsequently > in that dialog you may send a reINVITE, in which case you will have to > use the same URI as your From-URI.
Well, keeping the From/To URI within a dialog is not a requeriment now (RFC 4916 "Connected Identity") updates RFC 3261 and allows From/To URI to change. :) > I don't know if any of this affects what you are doing. No, in fact I'm not speaking about pure SIP but about XCAP. My doubt just concerns to the following scenario: - userA (SIP or TEL URI) wants to retrieve a XCAP document of userB (SIP or TEL URI). - userA generates a XCAP (HTTP) GET request and the XCAP server/proxy requires Digest authentication. - userA sets the credentials "username" field with its full URI. - Then the XCAP server inspects the HTTP URI by looking for the XUI URI (the URI of userB whose document is desired by userA). - The XCAP server checks the request authorization by inspecting both the originator (userA URI) and the destination (userB URI). - In order to check such authorization I must do a SIP/TEL URI's comparison (the coolest stuff in RFC 3261 !!). If these URI's have parameters the comparision is complex and the parser must be ready for URI's with parameters (and I would prefer to avoid it as I think it will never occur). As I said before, the only case in which I think it could make sense to have a URI with parameters is when a TEL URI with local number (so ";phone-context" is required) is used as userA or userB URI. Thanks a lot. -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
