[www-p3p-policy] <none>

>From rigo  Tue Sep 18 05:13:26 2001
Return-path: <rigo@tux.w3.org>
Envelope-to: rigo@localhost
Delivery-date: Tue, 18 Sep 2001 05:13:26 +0200
Received: from localhost ([127.0.0.1])
	by rigo with esmtp (Exim 3.31 #1 (Debian))
	id 15jBJv-00006n-03
	for <rigo@localhost>; Tue, 18 Sep 2001 05:13:11 +0200
Received: from www49.inria.fr [138.96.10.12]
	by localhost with POP3 (fetchmail-5.8.3)
	for rigo@localhost (single-drop); Tue, 18 Sep 2001 05:13:11 +0200 (CEST)
Received: from sophia.inria.fr by www49.inria.fr (8.11.1/8.10.0) with ESMTP id f8HKfa125831 for <rwenning@www49.inria.fr>; Mon, 17 Sep 2001 22:41:36 +0200 (MET DST)
Received: from tux.w3.org by sophia.inria.fr (8.11.1/8.10.0) with ESMTP id f8HKgHu21492 for <Rigo.Wenning@sophia.inria.fr>; Mon, 17 Sep 2001 22:42:17 +0200 (MET DST)
Received: (from rigo@localhost)
	by tux.w3.org (8.9.3/8.9.3) id QAA04057
	for Rigo.Wenning@sophia.inria.fr; Mon, 17 Sep 2001 16:42:16 -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 QAA04050
	for <rigo@w3.org>; Mon, 17 Sep 2001 16:42:16 -0400
Received: by www19.w3.org (8.9.0/8.9.0) id QAA19342
	for rigo@w3.org; Mon, 17 Sep 2001 16:42:15 -0400 (EDT)
Date: Mon, 17 Sep 2001 16:42:15 -0400 (EDT)
X-Envelope-From: www-p3p-policy-request@tux.w3.org  Mon Sep 17 16:42:04 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 QAA19321
	for <www-p3p-policy@www19.w3.org>; Mon, 17 Sep 2001 16:42:04 -0400 (EDT)
Received: from IMAIL13.innerhost.com (imail13.innerhost.com [207.21.208.42])
	by tux.w3.org (8.9.3/8.9.3) with ESMTP id QAA04023
	for <www-p3p-policy@w3.org>; Mon, 17 Sep 2001 16:42:04 -0400
Received: from alba [63.194.214.70] by IMAIL13.innerhost.com
  (SMTPD32-7.03) id A01A9930026; Mon, 17 Sep 2001 16:42:02 -0400
Message-ID: <017d01c13fb9$367b1460$46d6c23f@14designs.com>
From: "Lars Nyman" <larsnyman@14designs.com>
To: <www-p3p-policy@w3.org>
Old-Date: Mon, 17 Sep 2001 13:42:02 -0700
Organization: 14 Designs
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-Diagnostic: Not on the accept list
Subject: [Moderator Action] Number of policies that may apply
X-Diagnostic: Mail coming from a daemon, ignored
X-Envelope-To: www-p3p-policy
Resent-From: rigo@localhost
Resent-Date: Tue, 18 Sep 2001 06:29:29 +0200
Resent-To: www-p3p-policy@w3.org

Assume a user agent is retrieving an html entity by fetching a URI and that
a cookie is set by that html entity when it is returned by the server.

I am curious about how many policies may potentially apply in this situation
and how a user agent must determine which policy, or policies, applies.
Reading the P3P1.0 spec, I have come to the conclusion that two separate
policies may apply in this situation - one policy for the URI itself, and
another policy for the cookie being set when the entity referenced by the
URI is returned.  Is this correct?

If my conclusion is correct, that two separate policies may apply, that
would then imply that two different policy reference files may apply.  So my
second question is: must a user agent go through the same mechanisms twice
(as described in section 2.2)  in order to locate the two policy reference
files?

Lars Nyman

Received on Tuesday, 18 September 2001 06:02:36 UTC