This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 218 - Develop rationale for signed P3P policies
Summary: Develop rationale for signed P3P policies
Status: RESOLVED LATER
Alias: None
Product: P3P
Classification: Unclassified
Component: Signed P3P policies (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: P3P1.1
Assignee: Giles Hogben
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-28 13:09 UTC by Lorrie Cranor
Modified: 2003-05-28 17:12 UTC (History)
0 users

See Also:

Attachments

Description Lorrie Cranor 2003-05-28 13:09:12 UTC 
Before doing more work on signed P3P policies, we need to discuss whether there is 
really a compelling reason to do this.
Comment 1 Lorrie Cranor 2003-05-28 13:12:11 UTC 
The WG discussed this and decided that we don't currently see a compelling reason to 
pursue this.  http://www.w3.org/TR/xmldsig-p3p-profile/ already explains how digital 
signatures can be used in P3P. There might be some advantages to further 
standardization if there was a seal provider or other organization prepared to actually 
make use of this. However, until potential users come forward, there does not appear to 
be a need for further work on this.