I put together a short draft proposing a simple mechanism for allowing
end users to control policy for location URIs. Basically, wherever an
LCP has a slot for a location URI, we add a link for a "policy URI", and
define a very basic usage of HTTP for handling policy.
The one major thing that's missing from this draft is an extension of
this mechanism to non-LbyR policy -- to allow the Target to provision
policy related to third-party dereferences. At least in HELD, I think
this can be done by adding a similar policy URI link to the
<locationResponse> element (i.e., a reference to the *overall* policy
for theclinet). But I didn't feel like mhy XSD mojo was quite up to
defining this.
Comments welcome!
--Richard
-------- Original Message --------
Subject: New Version Notification for draft-barnes-geopriv-policy-uri-00
Date: Wed, 7 Oct 2009 10:00:55 -0700 (PDT)
From: IETF I-D Submission Tool <idsubmission@ietf.org>
To: rbarnes@bbn.com
A new version of I-D, draft-barnes-geopriv-policy-uri-00.txt has been
successfuly submitted by Richard Barnes and posted to the IETF repository.
Filename: draft-barnes-geopriv-policy-uri
Revision: 00
Title: Location Configuration Extensions for Policy Management
Creation_date: 2009-10-07
WG ID: Independent Submission
Number_of_pages: 13
Abstract:
Current location configuration protocols are capable of provisioning
an Internet host with a location URI that refers to the host's
location. However, these protocols lack a mechnism for the htarget
host to inspect or set the privacy rules that are applied to the URIs
they distribute. This document extends the current location
configuration protocols to provide hosts with a reference to the
rules that are applied to a URI, so that the host can view or set
these rules.
The IETF Secretariat.
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
