Re: [Geopriv] SIP Location Conveyance: dereferencing location-by-reference
Andrew Newton <[email protected]>
| Newsgroups | gmane.ietf.sip,gmane.ietf.geopriv |
|---|---|
| Message-ID | <[email protected]> |
Brian Rosen wrote: > In sip-location-conveyance, we allow a URI in the Location header to provide > for location-by-reference. We must have some kind of text that says what > the recipient does with this URI. > > Our proposal is to change the ABNF, which currently allows this URI to be > AbsoluteURI (meaning any scheme) and replace it with HTTP/HTTPS only. Of > course, there would still be the cid: for message body identification. We > would then define a dereference process as doing an HTTP/HTTPS GET, with no > parameters, on the URI, and expect to receive in return a PIDF-LO, exactly > as it would appear in a body. The text would state MUST implement TLS, > except for the emergency case. The text would further state that additional > dereferencing procedures could be defined by a standards track RFC. I'm not sure it is as simple as this. What happens when a client gets a subscribable location reference URI via the L7-LCP, and puts that into a Location header in an INVITE? How is the subscription done with HTTP? -andy _______________________________________________ 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