Re: IETF privacy policy - update

Sam Hartman <hartmans-ietf@mit.edu> Wed, 07 July 2010 20:40 UTC

Return-Path: <hartmans@mit.edu>
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 53A1A3A68DD for <ietf@core3.amsl.com>; Wed, 7 Jul 2010 13:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.591
X-Spam-Level:
X-Spam-Status: No, score=-2.591 tagged_above=-999 required=5 tests=[AWL=-0.326, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 c3l7XS4AfqnE for <ietf@core3.amsl.com>; Wed, 7 Jul 2010 13:40:05 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by core3.amsl.com (Postfix) with ESMTP id 5D0353A68BC for <ietf@ietf.org>; Wed, 7 Jul 2010 13:40:05 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id A73F8203C7; Wed, 7 Jul 2010 16:40:04 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id F197740D4; Wed, 7 Jul 2010 16:40:00 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Ole Jacobsen <ole@cisco.com>
Subject: Re: IETF privacy policy - update
References: <7022DEA1-7FC0-4D77-88CE-FA3788720B43@cdt.org> <8FBEA0C7-9B80-4860-AFAE-FB5A19E660EF@muada.com> <4C33A406.1090801@bogus.com> <BBDFC939-2109-41BB-B4E1-BE2CEE43B8CA@muada.com> <9C72FA78-C9C2-4719-9BFD-112ABEFA7117@cdt.org> <56522CF0-088B-4027-AF45-A6075A7EA666@muada.com> <51D591B3-1954-47A6-A40A-7DCE6DDD5CF0@cdt.org> <A68985E3-A34B-47AB-A6A2-E6718E505652@muada.com> <B75D4F49-2361-4706-A24A-D5E7026EE58D@cdt.org> <573C3FFA-B8CA-4B71-9128-07863DF1CF2B@muada.com> <tsl630r6pj1.fsf@mit.edu> <Pine.GSO.4.63.1007071250260.20133@pita.cisco.com>
Date: Wed, 07 Jul 2010 16:40:00 -0400
In-Reply-To: <Pine.GSO.4.63.1007071250260.20133@pita.cisco.com> (Ole Jacobsen's message of "Wed, 7 Jul 2010 12:53:28 -0700 (PDT)")
Message-ID: <tsllj9n58m7.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, Sam Hartman <hartmans-ietf@mit.edu>, IETF-Discussion list <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, 07 Jul 2010 20:40:06 -0000

>>>>> "Ole" == Ole Jacobsen <ole@cisco.com> writes:

    Ole> Sam,

    Ole> I view this more or less as "standard boilerplate", something
    Ole> you find in a lot of "online places". I think it is reasonable
    Ole> to expect that if you register for a meeting your personal info
    Ole> (e-mail address mostly) won't be sold/used/harvested by someone
    Ole> for purposes other than what you think you signed up for. It's
    Ole> probably useful for us to have such a statement.

I agree with the above.  however, the above doesn't sound like a
compelling justification to develop or review such a statement--just a
reason why we wouldn't mind having one.

For the development cost,  I don't care if people who want such a
statement go off and build one.

however, at least the IAOC has to review it.  I don't think that the
above justification is sufficient to place the review very high on the
priority list, nor do I think that in this instance the fact that
someone goes and spends time developing it should raise the review
priority. If the IAOC believes it needs to suck the rest of us into a
review, I think that pushes the priority even lower.

Now, there are things that in my mind would push the priority up:

* The IAOC isn't sure whether to use information in some way

* The community and IAOC disagree about how information is being used

* Something else