Re: [Geopriv] Fwd: I-D Action:draft-ietf-geopriv-arch-00.txt

I was wondering when this would come up. I don't think that it's strictly an LS, because it doesn't necessarily provide a LO. All it does is possibly enable the later acquisition of an LO. If we look at possession model, it's much closer to an LS than with authorization - where the actual LS might reject a request for the LO.

In the end, I don't think that it's overly important. By labelling it an LS, all the LS responsibilities go along with that and that could be helpful. I can't think of any reason not to simply label it as an LS.

--Martin

> I have a more meta question that's a hole in the above "inserter" role
> though:
>
> what is the role of the SIP server that inserts a location URI
> of
> the Target?
>
> that's gotta be defined somewhere. I believe this entity is also an
> LS, because it is a location aware entity that is sighting (put aside
> the fact that you hate that word) the target. This "act of sighting"
> is location awareness - ergo an entity role within Geopriv
> architecture. This entity would _not_, however, be an LG (that's
> saved for LO creators, which this entity does not do).
>
> James

------------------------------------------------------------------------------------------------
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]
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv