IETF Logo Mail Archive

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

Joel Jaeggli <joelja@bogus.com> Mon, 12 July 2010 21:52 UTC

Return-Path: <joelja@bogus.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 7A2723A6B63 for <ietf@core3.amsl.com>; Mon, 12 Jul 2010 14:52:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 ApyVw6MKvKEh for <ietf@core3.amsl.com>; Mon, 12 Jul 2010 14:52:18 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 5AFC03A6A05 for <ietf@ietf.org>; Mon, 12 Jul 2010 14:52:18 -0700 (PDT)
Received: from dhcp-92.nokia.net (dhcp-92.nokia.net [192.103.16.92] (may be forged)) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id o6CLqOeI050107 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 12 Jul 2010 21:52:24 GMT (envelope-from joelja@bogus.com)
Message-ID: <4C3B8E97.4040804@bogus.com>
Date: Mon, 12 Jul 2010 14:52:23 -0700
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.4) Gecko/20100608 Thunderbird/3.1
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: Comments on <draft-cooper-privacy-policy-01.txt>
References: <201007122134.o6CLY1rn023331@fs4113.wdf.sap.corp>
In-Reply-To: <201007122134.o6CLY1rn023331@fs4113.wdf.sap.corp>
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.2.2 (nagasaki.bogus.com [147.28.0.81]); Mon, 12 Jul 2010 21:52:24 +0000 (UTC)
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: Mon, 12 Jul 2010 21:52:19 -0000

On 7/12/10 2:34 PM, Martin Rex wrote:
> todd glassey wrote:
>> Martin Rex wrote:
>>> Some people seem to hope that creation of a "privacy policy" is going
>>> to improve things.  Personally, I don't think so.
>>
>> You mean that you think change that will protect the disclosure of
>> identities and proper notice as to who people represent is a bad thing?
>
> If there is no written privacy policy, then one has to make assumption
> about the consent on the use of PII.  And if the assumption is
> conservative (as I think it has been in the IETF), then it is going
> to be in the interest of the data subject, and if unclear, one
> should resort to ask the data subject (= opt-in).

have we all read the note well?

http://www.ietf.org/about/note-well.html

	Your ietf contribution will be made public.

	It was accepted by everyone who registered for the meeting.

"All IETF Contributions are subject to the rules of RFC 5378 and RFC 
3979 (updated by RFC 4879)."

etc.

While it is technically possible to attend an IETF meeting without 
making a contribution what exactly is the point in doing so? you can 
save a few thousand dollars by staying home and listening to the recordings.

v2.23.0 | Report a Bug | By Email