Re: Re: [Geopriv] SIP Location Conveyance: dereferencing location-by-reference

"James M. Polk" <[email protected]>
Newsgroups gmane.ietf.sip,gmane.ietf.geopriv
Message-ID <[email protected]>
At 05:25 PM 7/18/2006 -0400, Andrew Newton wrote:


>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,

you mean a SIP or SIPS URI?

You expect SIP to be a dereference capable protocol?  Why?

>and puts that into a Location header in an INVITE?

INVITEs don't do subscriptions, SUBSCRIBEs do, so this L7 value put into a 
Location header that's in an INVITE wouldn't create a subscription in the 
first place.

The above offering is to make sure dereferencing is done with HTTP/HTTPS, 
not SIP.

>  How is the subscription done with HTTP?

It isn't done with an INVITE either. sorry...


>-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

_______________________________________________
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
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.