Re: IETF privacy policy - still a bad idea

Phillip Hallam-Baker <hallam@gmail.com> Wed, 21 July 2010 23:24 UTC

Return-Path: <hallam@gmail.com>
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 D3E6E3A6863 for <ietf@core3.amsl.com>; Wed, 21 Jul 2010 16:24:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.938
X-Spam-Level:
X-Spam-Status: No, score=-1.938 tagged_above=-999 required=5 tests=[AWL=0.661, BAYES_00=-2.599]
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 uRzK1zqA1VC4 for <ietf@core3.amsl.com>; Wed, 21 Jul 2010 16:24:37 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id A35693A6824 for <ietf@ietf.org>; Wed, 21 Jul 2010 16:24:36 -0700 (PDT)
Received: by iwn38 with SMTP id 38so7930811iwn.31 for <ietf@ietf.org>; Wed, 21 Jul 2010 16:24:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=MUKymmYmjGD4sFlMYckkLXuIa7s7RbBD3UyVtO8PAAE=; b=lBBrDIYPBV7VlUjrWx9Km2nqi+eED21zgbv5VAMV+/WQVi/su4zqYq0SgsAwVuZXwS HYwbjsQ8M5uiLulrejynhpFxxbv4s/8EaUHb7b6sahIaz3kU4Si686GW/JmoF+Fpgi4p ok/yPw15ySwgjz4QchHtr+Q4h5JS5dDVwd3cg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=JTJyFfZstnJQYyFjuaIh6UB1f5TftRIryRMos5rtaOOqNSio7KLsqWJkhlupuYJ/sT AQnNSMns6bcz/XDKD3DqSH9IjaVwRPB/pKaJQQQoVSPz/bn5AlxWmxvjV9dmpFUsN5qi mxm3LW/cXQzmoyMeFKOx/j6ZNCyZeBlwBzG9Y=
MIME-Version: 1.0
Received: by 10.231.173.145 with SMTP id p17mr942067ibz.32.1279754692897; Wed, 21 Jul 2010 16:24:52 -0700 (PDT)
Received: by 10.231.10.76 with HTTP; Wed, 21 Jul 2010 16:24:52 -0700 (PDT)
In-Reply-To: <20100721223355.1728.qmail@joyce.lan>
References: <23A0C2B7-9EAC-4C84-8D4F-C18FB2590991@cdt.org> <20100721223355.1728.qmail@joyce.lan>
Date: Wed, 21 Jul 2010 19:24:52 -0400
Message-ID: <AANLkTin5fyqAenZU6PfLw2Ouy0jk-HdicK_WHweODmjq@mail.gmail.com>
Subject: Re: IETF privacy policy - still a bad idea
From: Phillip Hallam-Baker <hallam@gmail.com>
To: John Levine <johnl@iecc.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 22 Jul 2010 07:47:58 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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: Wed, 21 Jul 2010 23:24:38 -0000

My memory of partnership law is that if an agreement has the form of a
partnership it is a partnership regardless of claims in the contract
document explicitly stating it is not. It does not seem very likely
that the courts would take a different line with respect to
organizations that claim not to be organizations.

There may be some ambiguity as to what the status of the IETF is, but
that does not help.

Exceptionalism really does not work very well as a legal strategy.

On Wed, Jul 21, 2010 at 6:33 PM, John Levine <johnl@iecc.com> 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
> b) the IETF has no employees
> c) the IETF signs no contracts
>
> It would be helpful for someone, anyone, to explain in terms specific
> to the IETF what a privacy policy will accomplish.  Please be sure to
> make no references whatsoever to any other organization, since none of
> them are (un)organized like the IETF is.  While you're at it, be sure
> not to use the word "obvious" or its synonyms.
>
> I could be persuaded that there is a reason to have a privacy policy,
> but everything I've seen so far has been a combination of faulty
> analogies and mistaken premises.
>
> R's,
> John
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>



-- 
Website: http://hallambaker.com/