expiry doubt
"Elena" <[email protected]> Thu, 11 Jul 2002 12:13:34 +0200
| Newsgroups | gmane.comp.web.p3p.devel |
|---|---|
| Message-ID | <003f01c228c3$9d4b80a0$112abf8b@pcdsa17> |
This is a multi-part message in MIME format.
------=_NextPart_000_003C_01C228D4.60CCAF80
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
I've got a question on the expiration date of the policies. What I =
evinced from P3P specs is what follows:
1) Policy Reference File : if the POLICY-REFERENCES node has the EXPRY =
node as a child, then - for all the policy references that follow - the =
expiration date is computed using the info carried in the EXPIRY node. =
Otherwise, such policy references have a 24-hours validity.
2) Policy: if the POLICIES node (that MUST appear in any xml file =
representing a policy) has the EXPRY node as a child, then the policy =
expiration date is computed using the info carried in the EXPIRY node. =
Otherwise, the policy has a 24-hours validity.
So, in both cases, we have 2 ways to compute the expiration of a =
policy/policy ref file.
I've encountered a Policy Ref File with the following structure, that =
made me think about a third way:
<POLICY-REFERENCES>
<EXPIRY max-age=3D"86400 " />
<POLICY-REF about=3D"#XYZ">
<INCLUDE>/*</INCLUDE>
</POLICY-REF>
</POLICY-REFERENCES>
<POLICIES xmlns=3D"http://www.w3.org/2002/01/P3Pv1">
<POLICY name=3D"XYZ">
.....
....
</POLICY>
</POLICIES>
The POLICIES node doesn't have an EXPIRY node, so - according to P3P =
Recommendation - all the POLICY it embeds should be treated as having a =
24-hours validity.
However, I was wondering if - since the POLICIES node is inside the =
Policy Reference File - we should use the EXPIRY node inside the =
POLICY-REFERENCES to compute the POLICY validity.
Maybe this sounds crazy, and it doesn't make great sense to me too, but =
I would like to have this point clear.
Thanks a lot
------=_NextPart_000_003C_01C228D4.60CCAF80
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> I've got a question =
on the=20
expiration date of the policies. What I evinced from P3P specs is what=20
follows:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>1) Policy Reference File : </FONT><FONT =
face=3DArial=20
size=3D2>if the POLICY-REFERENCES node has the EXPRY node as a child, =
then - for=20
all the policy references that follow - the expiration date is =
computed=20
using the info carried in the EXPIRY node. Otherwise, such policy=20
references have a 24-hours validity.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>2) Policy: if the POLICIES node (that =
MUST appear=20
in any xml file representing a policy) has the EXPRY node as a child, =
then=20
the policy expiration date is computed using the info carried in =
the EXPIRY=20
node. Otherwise, the policy has a 24-hours validity.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>So, in both cases, we have 2 ways to =
compute the=20
expiration of a policy/policy ref file.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I've encountered a Policy Ref File with =
the=20
following structure, that made me think about a third way:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><POLICY-REFERENCES><BR><EXPIRY =
max-age=3D"86400 " /><BR><POLICY-REF=20
about=3D"#XYZ"><BR><INCLUDE>/*</INCLUDE><BR></POLICY-RE=
F><BR></POLICY-REFERENCES><BR><POLICIES=20
xmlns=3D"<A=20
href=3D"http://www.w3.org/2002/01/P3Pv1">http://www.w3.org/2002/01/P3Pv1<=
/A>"><BR><POLICY=20
name=3D"XYZ"></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>.....</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>....</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></POLICY></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></POLICIES></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The POLICIES node doesn't have an =
EXPIRY node, so -=20
according to P3P Recommendation - all the POLICY it embeds should be =
treated as=20
having a 24-hours validity.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>However, I was wondering if - since the =
POLICIES=20
node is inside the Policy Reference File - we should use the EXPIRY node =
inside=20
the POLICY-REFERENCES to compute the POLICY validity.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Maybe this sounds crazy, and it doesn't =
make great=20
sense to me too, but I would like to have this point =
clear.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Thanks a lot</FONT></DIV>
<DIV><FONT face=3DArial =
size=3D2></FONT> </DIV></FONT></DIV></BODY></HTML>
------=_NextPart_000_003C_01C228D4.60CCAF80--