Re: [secdir] E2MD BOF

Samuel Weiler <weiler@watson.org> Fri, 19 March 2010 03:49 UTC

Date: Thu, 18 Mar 2010 23:49:11 -0400
From: Samuel Weiler <weiler@watson.org>
To: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <ECABA224-C533-43A6-A888-C0F8097A145B@cisco.com>
Message-ID: <alpine.BSF.2.00.1003182344390.13633@fledge.watson.org>
References: <ECABA224-C533-43A6-A888-C0F8097A145B@cisco.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Cc: saag@ietf.org, secdir@ietf.org
Subject: Re: [secdir] E2MD BOF
Precedence: list
Reply-To: secdir-secretary@mit.edu

Cullen,

I suggest taking this question to the DNSEXT WG.  AFAIK, the DNSEXT 
agenda in Anaheim still has two minutes left open, which is about all 
the WG will tolerate of this.  :-)

-- Sam

On Wed, 17 Mar 2010, Cullen Jennings wrote:

> The E2MD BOF is wrestling with some complicated issues around 
> putting personal data about individuals in DNS (names, phones 
> numbers etc). They are considering various approaches to constrain 
> access to the private data. The leading contender as far as I can 
> tell is to only run the DNS with the private data in a walled garden 
> and make sure no one that should not see the data can query a server 
> in the walled garden. One or two people have mentioned you might 
> want to encrypt the private data and control access to the keys but 
> that idea has not received much discussion. It seems to me like a 
> possibility worth exploring a little.
>
> If anyone is interested or has spend time thinking about privacy of 
> data in DNS, input from folks on this list would be valuable and I 
> hope at least a few security folks can show up at the BOF.
>
> Thanks, Cullen
>
> Mailing list archive at http://www.ietf.org/mail-archive/web/e2md/index.html

[secdir] E2MD BOF Cullen Jennings
Re: [secdir] E2MD BOF Samuel Weiler