RE: [Geopriv] Re: teasing apart: http as a GEOPRIV using protocol

A using protocol carries location between a server and a watcher.  That is
PRECISELY what a dereference is.  Dereferencing protocols MUST be using
protocols.

However, I think that if the reference is a presence URI (sip/sips/pres)
then these issues are addressed.  If there is to be some other protocol used
to dereference, then it has to be a using protocol, and these issues must be
addressed.  If the protocol always returns a PIDF, many of these issues can
be answered by using the PIDF mechanisms to express user rules.

Now, for Presence (asserted by a proxy):
> 
> * We assume that it gets the location information somehow. Not further
> specified and might depend on the deployment environment.
Yeah, with the identifier mess

> 
> * What is the "entity" attribute of the 'presence' element?
The user, just as it would be if the endpoint asserted it, possibly
anonymized as we discussed.  I think the latter is more appropriate when
used in a Location header.  
> 
> * Where does the content for the usage-rules (e.g,
> 'retransmission-allowed', 'retention-expires', 'ruleset-reference',
> 'note-well') come from?
>From the user, just as it would be if the user asserted it.  It's just a
different mechanism for sending the same data.  Probably actually has the
same user interface, it's just the difference between whether the prototype
PIDF that the location is laid into gets sent to the phone or the proxy.
The UI to do this is a probably a web browser.
> 
> >


_______________________________________________
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