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

I see no harm in simplifying the header to be just 'absoluteURI' as in RFC 3986.  Text in the document can say that implementations MUST support https: and cid: (with appropriate cautions regarding the degenerate case of http:).

Andy,

Discussions to date on a subscription URI indicate that it is for LIS -> Target purposes only.  We have not yet reached the point where we discuss the creation of a reference.  There are obvious similarities, but I think that we would need to resolve some privacy and security concerns first.

> -----Original Message-----
> From: Andrew Newton [mailto:[email protected]]
> Sent: Wednesday, 19 July 2006 7:25 AM
> To: Brian Rosen
> Cc: [email protected]; [email protected]
> Subject: Re: [Geopriv] SIP Location Conveyance:dereferencing location-by-
> reference
> 
> 
> 
> 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
> 
> 
> _______________________________________________
> Geopriv mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/geopriv

------------------------------------------------------------------------------------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.  
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------------------------------
[mf2]

_______________________________________________
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