The only thing the P3P initiative requires is that a site 
have a privacy policy available online. P3P doesn't care 
one whit what that policy is. I personally consider P3P a 
complete waste of time as a means of protecting users' 
privacy. And IE6 actually *weakened* protection for its 
users' privacy by handing it off to P3P.

David
dvjones(at)ksbe.edu

On 18 Apr 2002, at 10:51, Mike Taylor wrote:

> The one IE 6 idiosyncrasy that caused us the most grief was actually its
> built-in privacy engine.  It adopts the P3P privacy policy standard
> established by W3C, and let me tell you this:  they claim establishing a P3P
> privacy policy is voluntary...but only if you want some of your potential
> customers to be unable to order off your online store because it blocks
> cookies under certain conditions.
> 
> We found that, unless we initiated a P3P privacy policy, some of our own
> cookies (not true third-party ones) were being blocked by IE 6.  Why?
> Because our secure server resides on a domain other than what our main site
> is, and we embed them both using frames.
> 
> The whole "how and why" of setting up a P3P privacy is needlessly
> convoluted:   you have to either know exactly what the XML tags are to build
> your own XML-based privacy policy, compact privacy policy (which has to be
> installed in the HTTP headers of your server) and a "human readable" privacy
> file, all located in folder off your web server's root named "W3C".
 

• Web Designer Courses
• Off the Shelf Training Courses

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA