To:
"'Edward Lewis'" <edlewis@arin.net>, ietf-provreg@cafax.se
From:
"Hollenbeck, Scott" <shollenbeck@verisign.com>
Date:
Mon, 31 Mar 2003 08:27:51 -0500
Sender:
owner-ietf-provreg@cafax.se
Subject:
RE: [ietf-provreg] the privacy problem statement
> Given that we've had a week to discuss the 'problem' and nothing > seems to have risen up to change it (EBW's comments notwithstanding), > I think it's safe to assume that the problem is as stated. > > IOW - Let's start looking at the solution. > > 'Course, it's never to complain about the problem statement. I just > want to throw open the doors on proposed answers... I'd like to propose a solution first described on the mailing list in December: http://www.cafax.se/ietf-provreg/maillist/2002-12/msg00093.html With a slight modification as proposed by Janusz: http://www.cafax.se/ietf-provreg/maillist/2002-12/msg00102.html The element structure could look like this: <contact:disclose flag="0"> <contact:email> <contact:voice> </contact:disclose> The above means that the email address and voice telephone numbers should not be disclosed (I've modified Janusz' proposal slightly to use a boolean value for the flag instead of a yes/no enumeration to simply the schema a bit). Server policy would determine the default value for disclosure if the <contact:disclose> element is not provided. If I remember correctly the feeling of the room in San Francisco was that this could be limited to the contact mapping. -Scott-