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

The original message said:
  The text would further state that additional dereferencing procedures
  could be defined by a standards track RFC.

Therefore, the proposed L7 protocol could specify its own dereference
procedure, including a subscription process.  We already have the mechanisms
needed to get a presence subscription out of an AoR.

Given the security concerns about location, it does seem wise to restrict
what kind of URI can be a location-by-reference to those that have reviews
of the geopriv privacy concerns.  I don't think we need to make the
mechanism completely general at the outset.  We propose to have the basic
mechanism be readily extensible by standards track RFCs.  That would seem to
balance security concerns against utility.

Brian

> -----Original Message-----
> From: Andrew Newton [mailto:[email protected]]
> Sent: Wednesday, July 19, 2006 12:51 PM
> To: James M. Polk
> Cc: Brian Rosen; [email protected]; [email protected]
> Subject: Re: [Sip] Re: [Geopriv] SIP Location Conveyance: dereferencing
> location-by-reference
> 
> James M. Polk wrote:
> > At 05:25 PM 7/18/2006 -0400, Andrew Newton wrote:
> >> 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?
> 
> I actually didn't mention SIP as the dereference protocol.  What I am
> asking is which dereference protocol with a subscription mechanism are
> you going to specify?  Or should implementers assume XMPP for this
> feature? :)
> 
> >> 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.
> 
> Thanks for the clarification, but I was talking about the dereference
> being orchestrated via subscription rather than polling.  I wasn't
> really talking about the conveyance itself, other than to ask how a
> conveyee is to know what to do with the reference.
> 
> > The above offering is to make sure dereferencing is done with
> > HTTP/HTTPS, not SIP.
> 
> I know, which is why I asked...
> 
> >>  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