Re: [Geopriv] REMINDER Re: WGLC: draft-ietf-geopriv-policy-17

["Kyle, Martin" <MartinKyle at SierraSystems.com>]

Hi Robert:
 
Perhaps, I am jumping into the fray without all the necessary context. However, when I read over the document with its intended purposes; it sounded a lot like an extension to the OASIS XACML Policy Language (http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xacml) called OGC GeoXACML (http://www.opengeospatial.org/standards/geoxacml) ... albeit privacy and authorization are different things; though, privacy may depend on an authorization mechanism.
 
>From draft-ietf-geopriv-policy-17.txt:
 
"This document defines an authorization policy language for controlling access to location information. It extends the Common Policy authorization framework to provide location-specific access control."
 
>From OGC GeoXACML standard:
 
"GeoXACML defines an extension to XACML for spatial data types and spatial authorization decision functions. Those data types and functions can be used to define additional spatial constraints for XACML based policies."
 
Clearly draft-ietf-geopriv-policy-17.txt appears to be built off of RFC 4745 while OGC GeoXACML is built off of OASIS XACML 2.0
 
The use cases that each address are identical in at least one case: "The rule set allows the entity that uses the rules defined in this document to restrict the retention and to enforce access restrictions on location data, including prohibiting any dissemination to particular individuals, during particular times or when the Target is located in a specific region."
 
The Geodetic Location Condition Profile seems quite anaemic from a geospatial perspective in that it only addresses one case (i.e. within - "Rule Makers use this profile by placing a GML [3] <Circle> element within the <location> element ") of the Egenhofer operators based on the 9-intersection model. The more robust set of operators are given URN references in the GeoXACML standard and thus allow other types of topological constraints to be encoded.
 
The various services (e.g. Location Server, Rule Maker) described in the draft-ietf-geopriv-policy-17.txt also seem to have corollaries in the OASIS XACML standard (e.g. Policy Decision Point, Policy Enforcement Point, Policy Administration Point, etc...).
 
As I do not know anything of merit in this domain, please consider my comments advisory only based on my background in geospatial web services. Indeed, you may have already considered the points that I raise.
 
Cheers,
 
Martin
 
H. Martin Kyle | Principal, GISP CASS
Sierra Systems

(T): 604-688-1371 (C): 778-384-5409 (F): 604-688-6482
1177 West Hastings Street, Suite 2500
Vancouver, BC V6E 2K3


Management Consulting | Project Implementation | Managed Services
website: www.SierraSystems.com <http://www.sierrasystems.com/> 

________________________________

From: geopriv-bounces at ietf.org on behalf of Robert Sparks
Sent: Mon 7/21/2008 9:01 AM
To: GEOPRIV
Subject: Re: [Geopriv] REMINDER Re: WGLC: draft-ietf-geopriv-policy-17



Note that we have hit the end of this WGLC period. There was 
frighteningly little response to the call.

Did people get to read this document and understand the changes that 
were made since we sent it up last? Please reply.

Based on offline communication, I believe Hannes has one last thing to 
double-check on. Unless there's controversy, I expect we will re-
request publication soon.

I'd be a _lot_ more comfortable with that if there were some list 
evidence that this version of the document has received sufficient 
review.

RjS


On Jul 11, 2008, at 1:44 PM, Robert Sparks wrote:

> Please send a note to the list when you've looked at this.
> "Good to go" comments are important to capture.
>
> RjS
>
> On Jun 30, 2008, at 3:32 PM, Robert Sparks wrote:
>
>> All -
>>
>> This is a GEOPRIV Working group last call for comments on:
>> http://www.ietf.org/internet-drafts/draft-ietf-geopriv-policy-17.txt
>>
>> This document has undergone extensive revision since this group 
>> requested its publication.
>> This version should represent closure on the many discussions that 
>> have taken place during its IETF and IESG review.
>>
>> Please give this document careful attention.
>>
>> Given that everyone is also preparing new drafts and getting ready 
>> for Dublin's meeting, this WGLC will last 3 weeks.
>> Please have your comments in by July 20.
>>
>> Thanks,
>>
>> RjS
>> _______________________________________________
>> Geopriv mailing list
>> Geopriv at ietf.org
>> https://www.ietf.org/mailman/listinfo/geopriv
>

_______________________________________________
Geopriv mailing list
Geopriv at ietf.org
https://www.ietf.org/mailman/listinfo/geopriv




----Notice Regarding Confidentiality----
This email, including any and all attachments, (this "Email") is intended only for the party to whom it is addressed and may contain information that is confidential or privileged.  Sierra Systems Group Inc. and its affiliates accept no responsibility for any loss or damage suffered by any person resulting from any unauthorized use of or reliance upon this Email.  If you are not the intended recipient, you are hereby notified that any dissemination, copying or other use of this Email is prohibited.  Please notify us of the error in communication by return email and destroy all copies of this Email.  Thank you.
_______________________________________________
Geopriv mailing list
Geopriv at ietf.org
https://www.ietf.org/mailman/listinfo/geopriv