Re: IETF privacy policy - still a bad idea

Dave CROCKER <dhc2@dcrocker.net> Thu, 22 July 2010 00:10 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 4C3F33A6B06 for <ietf@core3.amsl.com>; Wed, 21 Jul 2010 17:10:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.296
X-Spam-Level:
X-Spam-Status: No, score=-6.296 tagged_above=-999 required=5 tests=[AWL=0.303, 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 d02GXQMNpJJQ for <ietf@core3.amsl.com>; Wed, 21 Jul 2010 17:10:54 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 1B6843A6840 for <ietf@ietf.org>; Wed, 21 Jul 2010 17:10:54 -0700 (PDT)
Received: from [192.168.1.45] (ppp-68-122-73-240.dsl.pltn13.pacbell.net [68.122.73.240]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o6M0ArhD004533 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Jul 2010 17:10:58 -0700
Message-ID: <4C478C82.2020804@dcrocker.net>
Date: Wed, 21 Jul 2010 17:10:42 -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.7) Gecko/20100713 Thunderbird/3.1.1
MIME-Version: 1.0
To: John Levine <johnl@iecc.com>
Subject: Re: IETF privacy policy - still a bad idea
References: <20100721223355.1728.qmail@joyce.lan>
In-Reply-To: <20100721223355.1728.qmail@joyce.lan>
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]); Wed, 21 Jul 2010 17:10:59 -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, 22 Jul 2010 00:10:55 -0000

On 7/21/2010 3:33 PM, John Levine wrote:
>> You appear to be concerned about exposing the IETF to risk by the
>> adoption of a privacy policy (but apologies if I am misunderstanding
>> the concern you expressed).  The absence of a privacy policy, however,
>> actually increases risk to the IETF in at least three ways:
>
>   ... none of which applies since
>
> a) the IETF has no formal legal existence

With creation of the IETF Trust, that is no longer true.  There also have been 
comments from one or another attorney that the absence of formal legal formation 
is not the same as no "formal" legal existence.  All of which at least suggests, 
once again, that we ought to leave legal pronouncements to attorneys (and even 
then, seek a second opinion.)


> b) the IETF has no employees

Well, again, there's a formal correctness to that statement and a practical 
incorrectness.


> c) the IETF signs no contracts

I was under the impression that the IAOC now signs the event contracts. But 
perhaps that's not correct.


> It would be helpful for someone, anyone, to explain in terms specific
> to the IETF what a privacy policy will accomplish.

Ahh, well.  That's a good idea, not matter your earlier assertions.


d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net