Daniel

wow... you nailed this one quickly.

Neither the SIP WG nor Geopriv WG have a position with regard to this. I don't like the parameter at all, and have said so from its introduction into discussions about putting it in the draft. I don't think it accomplishes much more than confusion or a false sense of security by implementors.

That said, a proxy has "ar" capabilities wrt the Geolocation according to Table 1. (on page 7), and associated text states this pretty clearly. There is no text (not even a hint) that a proxy cannot read a location because "recipient=endpoint", therefore it can. I would take this "recipient=" parameter as a hint to each type of SIP entity that

        + if a UAS receives this parameter (meaning in a SIP request with
           a Geolocation header), and it is set to "recipient", the UAS
           shouldn't ignore the location in the request (like it otherwise
           might).

        + If a proxy receives this parameter (meaning in a SIP request with
           a Geolocation header), and it is set to "server", the proxy
           shouldn't ignore the location in the request (like it otherwise
           might).

I don't think either indication *ever* means the other SIP entity type cannot view the location, based on the parameter. The only exception I can think of is a Location-by-value hidden by S/MIME means no one save who has the decryption key can view the contents of what's encrypted.

Does this make sense?

James

At 04:59 AM 11/20/2007, Daniel Grotti wrote:
Hi all,
I'd like to ask a question about "draft-ietf-sip-location-conveyance-09.txt".

How does Proxy Server have to work when a Geolocation Header contain "recipient=endpoint" parameter ? Does the Proxy server just have to forward the SIP message (without do anything else) or can it read the information conveyed ?
thanks,
Regards
daniel

--

---------------------------------------------------
Daniel Grotti
DEIS - University of Bologna
Via Venezia, 52 - 47023 Cesena (FC) - ITALY

Contacts
e-mail : [EMAIL PROTECTED]
Skype name : Daniel Grotti
---------------------------------------------------



_______________________________________________
Sip mailing list  https://www1.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://www1.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

Reply via email to