To:
"'Eric Brunner-Williams in Portland Maine'" <brunner@nic-naa.net>
Cc:
"'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
From:
"Hollenbeck, Scott" <shollenbeck@verisign.com>
Date:
Fri, 6 Jul 2001 11:47:30 -0400
Sender:
owner-ietf-provreg@cafax.se
Subject:
RE: Data Collection Requirements
>-----Original Message----- >From: Eric Brunner-Williams in Portland Maine >[mailto:brunner@nic-naa.net] >Sent: Friday, July 06, 2001 10:58 AM >To: Hollenbeck, Scott >Cc: 'Eric Brunner-Williams in Portland Maine'; 'ietf-provreg@cafax.se'; >brunner@nic-naa.net >Subject: Re: Data Collection Requirements > > >Here is the DTD (circa fall 2000, so no Schema) we developed in the privacy >working group dealing with onward transfer (p3p policy presumed at the first >reseller-like web site, maintained and with jurisdictional "record route". >It is followed by the DTD (same date) defining the CPExchange P3P subset. >Similar work last October for the http state management mechanism (cookies) >was incorporated into P3P as "compact representations" at a late moment, and >I understand will be part of the MS IE offering -- that is, in-line DC policy >expressed in XML. Can you share an example XML _instance_ that's appropriate in the _provreg_ protocol context? I'd like to understand how this specifically applies to contact registration, for example. How do things work if the reseller doesn't consistently use a web interface to collect data? <Scott/>