Answer: IE6 will be supporting a feature that reads the machine readable P3P
policy of a web site. Depending on the settings in the options dialog, it may
disable certain features of the browser, such as the capability of setting
cookies, unless there is a P3P file in place, and the file matches the user's
preferences. So unless you implement a P3P policy on your web site, some users
may have a bad experience visiting your site.

These files must be created using the syntax given in the p3p specification. The
p3p specification is overly complex in my opinion, taking into account the most
horrendously complex privacy policy that you can imagine. I strongly suggest
using an editor, such as the IBM p3p editor mentioned in my first post, on the
subject to help you create them.

The editor will help you construct the correct syntax and descriptions. Setting
up the editor was tricky as you first had to install the java files from the
Sun site. The interface is consistent but a little weird. It gets the job done,
and is far easier than working through the p3p spec. I'll try to help with
questions about it if anyone has them.

Create a directory called /w3c off the root of your domain and locate all three
files in that directory.

Help user agents find the files. There are three ways that a web browser can use
to find the the files.

By looking for the /w3c directory

By looking at the HTTP header

By looking at a link tag within the file

It is suggested that you help the web browser with all three techniques. The
directory is already done. To do the HTTP header, you need to add a line that
makes it look like this:

P3P: policyref="/w3c/p3p.xml"

Now exactly how you do that depends on your web server. In Active Server Pages,
you can either configure IIS to do it in the IIS management dialogs, or you can
add the following line to the top of your ASP document: