[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Cc: "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
From: Ted Hardie <hardie@qualcomm.com>
Date: Wed, 16 Apr 2003 11:20:40 -0700
In-Reply-To: <200304161737.h3GHb9Zj003014@nic-naa.net>
Sender: owner-ietf-provreg@cafax.se
Subject: Re: [ietf-provreg] legal entity vs individual person


On Wednesday, April 16, 2003, at 10:37 AM, Eric Brunner-Williams in 
Portland Maine wrote:

>> One of the cases mentioned has been data for organizations
>> which implicitly identifies data about individual persons.  One of the
>
> solved by roles. janitor@ibm.com
>
>> common cases would be the single-individual consulting shop;
>> in that case you might argue that revealing this information is
>> a cost of doing business as a legal entity rather than as an
>> individual.  The
>
> solved by roles. janitor@gal-in-garage.com

Role contact information is a useful tool, but it does not achieve
the same thing as there some forms of contact for which
roles are not available.


>> hot-button cases, though, are those where revealing the information
>> has consequences for a third party.  The shelter example is the
>> one most commonly cited, where the decision to reveal information
>> about the shelter's business address or telephone number affects
>> those who seek its services.
>
> solved by pobox and hotline. see 
> http://www.cumberlandcounty.org/DAvr.html.

Assumes an infrastructure not uniformly present, and assumes that
use of that infrastructure does not carry second order threats.

>> Figuring out whether or not to support specific cases seems to me
>> a policy decision.   Having the hook for the different policies
>> seems reasonable enough; whether you cast it as "Privacy 
>> Considerations"
>> or "Client Data Control Considerations" doesn't really matter to me.
>
> I'm aware of that.
>
> Eric
>

						regards,
							Ted Hardie


Home | Date list | Subject list