location to any other entity, because an LS has to obtain location
somehow, and it does that by receiving location from an LG. The
definition of LG in geopriv-arch is explicit about this.
I also think I read the first paragraph differently. It doesn't say
that a LIS performs the LG role. It also doesn't say that a LIS
performs the LS role. It's a server in an access network that can
perform either role, or neither role. We discussed this before and
reached that conclusion: http://www.ietf.org/mail-archive/web/geopriv/current/msg07579.html
On Oct 20, 2009, at 11:50 PM, Thomson, Martin wrote:
> Hi Alissa,
>
> This looks good, except that I think that my comment was mostly
> addressed at the first sentence. I'd prefer:
>
> Some performing the Location _Server_ role are designed only to
> provide Targets with their own locations (as opposed to
> distributing a Target's location to others). ...
>
> Reason: I'm a nasty pedant.
>
> Or: The Location Server is the only role that provides location to
> any other entity. Consider the possibility that the entity
> providing location information did not generate it.
>
> (nit: The first paragraph could be three, given that it makes three
> distinct statements.)
>
> --Martin
>
>> -----Original Message-----
>> From: Alissa Cooper [mailto:acooper@cdt.org]
>> Sent: Tuesday, 20 October 2009 6:59 PM
>> To: Thomson, Martin
>> Cc: Marc Linsner; GEOPRIV
>> Subject: Re: [Geopriv] LCP & Arch....
>>
>> I realized that I had previously proposed an edit to this same
>> section
>> for a different reason (http://www.ietf.org/mail-
>> archive/web/geopriv/current/msg07828.html
>> ), and those changes are not reflected in the suggested text below.
>> So, putting it all together, here is what I think we have:
>>
>> 3.2.2. Location Configuration
>>
>> Some performing the Location Generator role are designed only to
>> provide Targets with their own locations (as opposed to
>> distributing
>> a Target's location to others). The process of providing a Target
>> with its own location is known within Geopriv as Location
>> Configuration. The term Location Information Server (LIS) is often
>> used
>> to describe the entity that performs this function (although a LIS
>> may also
>> perform other functions, such as providing a Target's location to
>> other entities). A Location Configuration Protocol (LCP) is one
>> mechanism that can be used by a Target to discover its own location
>> from a LIS. The LCP provides functions in the way it obtains,
>> transports and delivers
>> location requests and responses between the LIS and the Target such
>> that the LIS can trust that the location requests and responses
>> handled via the LCP are in fact from/to the Target. Several LCPs
>> have
>> been developed within Geopriv [9][10][11][12].
>>
>> A LIS whose sole purpose is to perform Location Configuration need
>> only follow a simple privacy-preserving
>> policy: transmit a Target's location only to the Target itself.
>> This
>> is known as the "LCP policy."
>>
>> Importantly, if an LS is also serving in the role of LG and it has
>> not been provisioned with Privacy Rules for a particular Target, it
>> MUST follow the LCP policy, whether it is a LIS or not. In the
>> positioning phase, an entity serving the roles of both LG and LS
>> that
>> has not received Privacy Rules must follow this policy. The same
>> is
>> true for any LS in the distribution phase.
>>
>>
>> I think this makes it clear that a LIS can serve the role of LG or of
>> LS.
>>
>> Alissa
>>
>>
>
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
