Re: Comments on <draft-cooper-privacy-policy-01.txt>

Dave CROCKER <dhc2@dcrocker.net> Thu, 15 July 2010 21:34 UTC

Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C07813A6B6E for <ietf@core3.amsl.com>; Thu, 15 Jul 2010 14:34:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hRteoOlNj6uj for <ietf@core3.amsl.com>; Thu, 15 Jul 2010 14:34:29 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 796EC3A6B99 for <ietf@ietf.org>; Thu, 15 Jul 2010 14:34:29 -0700 (PDT)
Received: from [192.168.43.47] (m700e36d0.tmodns.net [208.54.14.112]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o6FLYQ6n022415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Jul 2010 14:34:38 -0700
Message-ID: <4C3F7EDE.3010103@dcrocker.net>
Date: Thu, 15 Jul 2010 14:34:22 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.4) Gecko/20100608 Thunderbird/3.1
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Comments on <draft-cooper-privacy-policy-01.txt>
References: <7022DEA1-7FC0-4D77-88CE-FA3788720B43@cdt.org> <47076F01-CC4C-45E6-803E-8E2516BE15AC@gmail.com> <20100709113224.123900@gmx.net> <4C3A0C74.4080504@dcrocker.net> <4C3B2C5B.1040702@bogus.com> <m2d3usbrmg.wl%randy@psg.com> <4C3B541F.9020403@dcrocker.net> <m2vd8ijunr.wl%randy@psg.com> <4C3DAFFE.3080804@dcrocker.net> <EAE866037547F256DB9328FF@[172.16.31.124]> <4C3E405B.8040705@bbiw.net> <19BCD3B3F563125432C1311B@PST.JCK.COM>
In-Reply-To: <19BCD3B3F563125432C1311B@PST.JCK.COM>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 15 Jul 2010 14:34:40 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jul 2010 21:34:30 -0000

On 7/15/2010 9:42 AM, John C Klensin wrote:
> In principle, I'm in favor of having a published privacy policy.
...
    < extended repetition of based goals elided >
...
...
> IMO, those are the types of issues we should be discussing and
> that several people on the list have been discussing.
> Hyperbole, wild extrapolations, assumptions that network
> research (even if it were occurring) was actually research on
> human subjects, unfounded accusations about bad behavior or
> hidden conspiracies, etc., don't further that discussion.

Anyone who has dealt with a human subjects review panels would wish to be as 
dismissive of them as you are.  But it's a serious topic and I offered it 
seriously.  Perhaps the scope of the IETF's privacy work does not need to 
include it.  But perhaps it does.  The discussion was raising areas of concern. 
  I offered one more.

That you might believe it doesn't fall within scope is fine, although I'll 
suggest that such an opinion is always strengthened when accompanied by 
considered reasons, rather than being facilely to lump them in with red-flag 
labels like hyperbole.  (If you wish to address thread activity involving those 
red-flag behaviors, please direct your mail to your buddy.)

That anyone would be so mechanically dismissive of this issue underscores the 
challenges of discussing privacy in this community.

I explained why I thought the issue was worth considering along with the rest of 
the concerns about privacy.  I didn't generate the reference to doing research 
and I didn't generate the reference to unauthorized disclosure of personal data.

So please do feel free to respond with relevant substance rather than a quick 
hand wave.


>     It is also
> relevant that what was disclosed, if I recall, were passwords.
> Not password-user pairs or anything else that would constitute
> what is normally considered personally identifiable information.

OK.  And none of those passwords were sufficient to identify their owner, right?


d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net