W3C home > Mailing lists > Public > www-p3p-public-comments@w3.org > September 2001

[www-p3p-public-comments] <none>

From: Rigo Wenning <rigo@w3.org>
Date: Wed, 26 Sep 2001 07:32:10 +0200
Message-Id: <E15m7Io-0000BO-00@localhost>
To: www-p3p-public-comments@w3.org
>From rigo  Wed Sep 26 07:30:15 2001
Return-path: <rigo@tux.w3.org>
Envelope-to: rigo@localhost
Delivery-date: Wed, 26 Sep 2001 07:30:15 +0200
Received: from localhost ([127.0.0.1])
	by localhost with esmtp (Exim 3.32 #1 (Debian))
	id 15m7Gx-00006Y-01
	for <rigo@localhost>; Wed, 26 Sep 2001 07:30:15 +0200
Received: from www49.inria.fr [138.96.10.12]
	by localhost with POP3 (fetchmail-5.8.3)
	for rigo@localhost (single-drop); Wed, 26 Sep 2001 07:30:15 +0200 (CEST)
Received: from sophia.inria.fr by www49.inria.fr (8.11.1/8.10.0) with ESMTP id f8PLnp123542 for <rwenning@www49.inria.fr>; Tue, 25 Sep 2001 23:49:51 +0200 (MET DST)
Received: from tux.w3.org by sophia.inria.fr (8.11.1/8.10.0) with ESMTP id f8PLoXw15747 for <Rigo.Wenning@sophia.inria.fr>; Tue, 25 Sep 2001 23:50:33 +0200 (MET DST)
Received: (from rigo@localhost)
	by tux.w3.org (8.9.3/8.9.3) id RAA14965
	for Rigo.Wenning@sophia.inria.fr; Tue, 25 Sep 2001 17:50:32 -0400
Received: from www19.w3.org (www19.w3.org [18.29.0.19])
	by tux.w3.org (8.9.3/8.9.3) with ESMTP id RAA14959
	for <rigo@w3.org>; Tue, 25 Sep 2001 17:50:32 -0400
Received: by www19.w3.org (8.9.0/8.9.0) id RAA24995
	for rigo@w3.org; Tue, 25 Sep 2001 17:50:31 -0400 (EDT)
Date: Tue, 25 Sep 2001 17:50:31 -0400 (EDT)
X-Envelope-From: www-p3p-public-comments-request@tux.w3.org  Tue Sep 25 17:50:16 2001
Received: from tux.w3.org (tux.w3.org [18.29.0.27])
	by www19.w3.org (8.9.0/8.9.0) with ESMTP id RAA24974
	for <www-p3p-public-comments@www19.w3.org>; Tue, 25 Sep 2001 17:50:16 -0400 (EDT)
Received: from cn-sfo1-g7.cnet.com (64.125.251.137.available.above.net [64.125.251.137] (may be forged))
	by tux.w3.org (8.9.3/8.9.3) with ESMTP id RAA14907
	for <www-p3p-public-comments@w3.org>; Tue, 25 Sep 2001 17:50:15 -0400
Received: from cnet23.cnet.cnwk (cnet23.cnet.com [10.10.40.28])
	by cn-sfo1-g7.cnet.com (8.9.3/8.9.3) with ESMTP id OAA23043
	for <www-p3p-public-comments@w3.org>; Tue, 25 Sep 2001 14:49:44 -0700 (PDT)
Received: by cnet23.cnet.cnwk with Internet Mail Service (5.5.2653.19)
	id <S4W0JS12>; Tue, 25 Sep 2001 14:49:44 -0700
Message-ID: <F5E5CB897FCA1A4BAC3FD38CEBA1A644F917CD@zdnet08.zdz.cnwk>
From: Clifford Lyon <Clifford.Lyon@cnet.com>
To: "'www-p3p-public-comments@w3.org'" <www-p3p-public-comments@w3.org>
Old-Date: Tue, 25 Sep 2001 14:47:39 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1460B.B2AE8190"
X-Diagnostic: Not on the accept list
Subject: [Moderator Action] dynamic.cookies vs. <COOKIE-INCLUDE>
X-Diagnostic: Mail coming from a daemon, ignored
X-Envelope-To: www-p3p-public-comments
Resent-From: rigo@localhost
Resent-Date: Wed, 26 Sep 2001 07:32:10 +0200
Resent-To: www-p3p-public-comments@w3.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1460B.B2AE8190
Content-Type: text/plain;
	charset="iso-8859-1"

Hi,

Referring to the policy reference file, the current working 
draft 24 Sept 2001 says:

> Note that the set of URIs specified with INCLUDE 
> and EXCLUDE does not include cookies that might 
> be triggered when requesting one of such URIs: 
> in order to associate policies with cookies, the 
> COOKIE-INCLUDE and COOKIE-EXCLUDE elements are needed.

My question is, if the "dynamic.cookies" value is specifed
in the base data schema, and the information linked-to and 
contained-in a cookie is covered in the policy, doesn't that
policy then cover cookies set when requesting the URI 
associated with the policy? Or does the cookie-include
still need to appear?

Thanks,

cpl.



------_=_NextPart_001_01C1460B.B2AE8190
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>dynamic.cookies vs. &lt;COOKIE-INCLUDE&gt;</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Hi,</FONT>
</P>

<P><FONT SIZE=2>Referring to the policy reference file, the current working </FONT>
<BR><FONT SIZE=2>draft 24 Sept 2001 says:</FONT>
</P>

<P><FONT SIZE=2>&gt; Note that the set of URIs specified with INCLUDE </FONT>
<BR><FONT SIZE=2>&gt; and EXCLUDE does not include cookies that might </FONT>
<BR><FONT SIZE=2>&gt; be triggered when requesting one of such URIs: </FONT>
<BR><FONT SIZE=2>&gt; in order to associate policies with cookies, the </FONT>
<BR><FONT SIZE=2>&gt; COOKIE-INCLUDE and COOKIE-EXCLUDE elements are needed.</FONT>
</P>

<P><FONT SIZE=2>My question is, if the &quot;dynamic.cookies&quot; value is specifed</FONT>
<BR><FONT SIZE=2>in the base data schema, and the information linked-to and </FONT>
<BR><FONT SIZE=2>contained-in a cookie is covered in the policy, doesn't that</FONT>
<BR><FONT SIZE=2>policy then cover cookies set when requesting the URI </FONT>
<BR><FONT SIZE=2>associated with the policy? Or does the cookie-include</FONT>
<BR><FONT SIZE=2>still need to appear?</FONT>
</P>

<P><FONT SIZE=2>Thanks,</FONT>
</P>

<P><FONT SIZE=2>cpl.</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C1460B.B2AE8190--
Received on Wednesday, 26 September 2001 07:06:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.1 : Tuesday, 21 September 2004 12:14:17 GMT