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

[www-p3p-dev] <none>

From: Rigo Wenning <rigo@w3.org>
Date: Fri, 28 Sep 2001 11:33:11 +0200
Message-Id: <E15mu19-0000V3-00@localhost>
To: www-p3p-dev@w3.org
>From rigo  Fri Sep 28 10:47:14 2001
Return-path: <rigo@tux.w3.org>
Envelope-to: rigo@localhost
Delivery-date: Fri, 28 Sep 2001 10:47:14 +0200
Received: from localhost ([127.0.0.1])
	by localhost with esmtp (Exim 3.32 #1 (Debian))
	id 15mtIg-0000R6-00
	for <rigo@localhost>; Fri, 28 Sep 2001 10:47:14 +0200
Received: from www49.inria.fr [138.96.10.12]
	by localhost with POP3 (fetchmail-5.8.3)
	for rigo@localhost (single-drop); Fri, 28 Sep 2001 10:47:14 +0200 (CEST)
Received: from sophia.inria.fr by www49.inria.fr (8.11.1/8.10.0) with ESMTP id f8SDeE115754 for <rwenning@www49.inria.fr>; Fri, 28 Sep 2001 15:40:14 +0200 (MET DST)
Received: from tux.w3.org by sophia.inria.fr (8.11.1/8.10.0) with ESMTP id f8SDeuH21223 for <Rigo.Wenning@sophia.inria.fr>; Fri, 28 Sep 2001 15:40:57 +0200 (MET DST)
Received: (from rigo@localhost)
	by tux.w3.org (8.9.3/8.9.3) id JAA24567
	for Rigo.Wenning@sophia.inria.fr; Fri, 28 Sep 2001 09:40:56 -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 JAA24561
	for <rigo@w3.org>; Fri, 28 Sep 2001 09:40:55 -0400
Received: by www19.w3.org (8.9.0/8.9.0) id JAA02152
	for rigo@w3.org; Fri, 28 Sep 2001 09:40:54 -0400 (EDT)
Date: Fri, 28 Sep 2001 09:40:54 -0400 (EDT)
X-Envelope-From: www-p3p-dev-request@tux.w3.org  Fri Sep 28 09:40:44 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 JAA02119
	for <www-p3p-dev@www19.w3.org>; Fri, 28 Sep 2001 09:40:44 -0400 (EDT)
Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65])
	by tux.w3.org (8.9.3/8.9.3) with ESMTP id JAA24523
	for <www-p3p-dev@w3.org>; Fri, 28 Sep 2001 09:40:42 -0400
Received: from mrelay.jrc.it (localhost [127.0.0.1])
	by mrelay.jrc.it (LMC5614B) with ESMTP id f8SDedW27322
	for <www-p3p-dev@w3.org>; Fri, 28 Sep 2001 15:40:39 +0200 (MEST)
Received: from isis-ms.sti.jrc.it (isis-gs.sti.jrc.it [139.191.8.244])
	by mrelay.jrc.it (LMC5614A) with ESMTP id f8SDecJ27318
	for <www-p3p-dev@w3.org>; Fri, 28 Sep 2001 15:40:38 +0200 (MEST)
Received: from pcdsa22 ([139.191.42.22]) by isis-ms.sti.jrc.it
          (Netscape Messaging Server 4.15) with SMTP id GKDKNN00.029 for
          <www-p3p-dev@w3.org>; Fri, 28 Sep 2001 15:40:35 +0200 
Message-ID: <006c01c14823$45cecac0$162abf8b@pcdsa22>
From: "Giles Hogben" <giles@ontv.com>
To: "p3pdev" <www-p3p-dev@w3.org>
Old-Date: Fri, 28 Sep 2001 15:41:27 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Diagnostic: Not on the accept list
Subject: [Moderator Action] More sep spec qn's on pref
X-Diagnostic: Mail coming from a daemon, ignored
X-Envelope-To: www-p3p-dev
Resent-From: rigo@localhost
Resent-Date: Fri, 28 Sep 2001 11:33:11 +0200
Resent-To: www-p3p-dev@w3.org


In this example:

"Busy's privacy policy applies to the images hosted by CDN, so Busy uses the
HINT element in its policy reference file to point to a suitable policy
reference file at CDN, indicating that such images are covered by
busy.example.com P3P policy."

Why doesn't Busy just specify that the images are covered by example.com's
P3P policy in its own pref file, instead of using the hint mechanism?

Thanks

Giles Hogben
Received on Friday, 28 September 2001 11:07:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 18 June 2010 00:12:47 GMT