RE: [ietf-provreg] Question regarding contact:disclose behaviour.

["Hollenbeck, Scott" <shollenbeck@verisign.com>]

> -----Original Message-----
> From: owner-ietf-provreg@cafax.se 
> [mailto:owner-ietf-provreg@cafax.se] On Behalf Of Alexander Mayrhofer
> Sent: Tuesday, October 31, 2006 4:56 AM
> To: ietf-provreg@cafax.se
> Cc: Andreas Papst
> Subject: [ietf-provreg] Question regarding contact:disclose behaviour.
> 
> 
> Hi,
> 
> we're moving towards EPP enabling .at, but there is an open question
> regarding how "contact:disclose" should work (we are going to 
> use that for
> hiding certain elements in a legacy whois service). Section 
> 2.9 of RFC3733
> contains the following example about "contact:disclose":

[snip]

> I'd appreciate feedback on how that was originally intended, 
> and would like
> to see some clarifying text about this in 3733bis...

The text you're missing is already in 3733bis.  See the second paragraph
of section 2.9:

"A server operator announces a default disclosure policy when
establishing a session with a client.  When an object is created or
updated, the client can specify contact attributes that require
exceptional disclosure handling using an OPTIONAL <contact:disclose>
element."

and then in the third paragraph:

"A value of "true" or "1" (decimal one) notes a client preference to
allow disclosure of the specified elements as an exception to the stated
data collection policy.  A value of "false" or "0" (decimal zero) notes
a client preference to not allow disclosure of the specified elements as
an exception to the stated data collection policy."

The part you seem to have missed is the relationship with the data
collection policy (dcp) element that identifies the server operator's
default disclosure policy.  The contact:disclose element is used by the
client to identify a request for exceptions to the stated policy.
Elements not specified in the contact:disclose element remain subject to
the default policy.

-Scott-