W3C home > Mailing lists > Public > public-p3p-spec@w3.org > February 2006

policy expiry and update issues

From: Sören Preibusch <spreibusch@diw.de>
Date: 21-Feb-2006 13:29:35 CET
To: public-p3p-spec@w3.org
Message-ID: <OFF67333EE.3AE98884-ONC125711C.0044A061@diw.de>

In order to cope with policy update problems and the non-ambiguity problems
during policy transition phases (cf. section 2.4.1), the element EXPIRY
could be slightly modified and a new element LAUNCH could be introduced.

Actually, specifying relative expiry times longer than one day makes it
impossible to switch to a new policy and to be sure that there are no
cached policies no more identical to the newly deployed policy.

This issue could be addressed by allowing a simultaneous use of the ?date?
and the ?max-age? attributes of the EXPIRY element with the semantics:
?this policy / policy reference file is valid for the duration specified by
?max-age? but not after the date specified by ?date??.

In addition, the introduction of a new element LAUNCH as a companion to
EXPIRY could streamline the policy transition process. An attribute ?date?
indicates since when the policy will be valid. In written text privacy
policies, it is usual to indicate when they will come into effect. Multiple
policies with non-overlapping validity periods could be specified for a
same URI to handle policy transition.

Best wishes, Sören Preibusch.
Received on Tuesday, 21 February 2006 12:29:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:02:20 UTC