Re: Future Handling of Blue Sheets

Martin Rex <mrex@sap.com> Tue, 24 April 2012 22:17 UTC

Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E11221F85BD for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2012 15:17:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.121
X-Spam-Level:
X-Spam-Status: No, score=-10.121 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wcPaAOEMM0gp for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2012 15:17:18 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id A52FA21F85B4 for <ietf@ietf.org>; Tue, 24 Apr 2012 15:17:17 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q3OMHCGp012720 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 25 Apr 2012 00:17:12 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201204242217.q3OMHCls018770@fs4113.wdf.sap.corp>
Subject: Re: Future Handling of Blue Sheets
To: john-ietf@jck.com
Date: Wed, 25 Apr 2012 00:17:12 +0200
In-Reply-To: <D4345C087CD29FF2165406B7@JCK-EEE10> from "John C Klensin" at Apr 24, 12 05:27:44 pm
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 24 Apr 2012 22:17:18 -0000

John C Klensin wrote:
> 
>                                      I strongly encourage the
> IASA to avoid ever holding an IETF meeting in Germany again
> without first obtaining appropriate legal advice that it is
> acceptable given our existing conditions to record the names and
> identities of anyone participating in any IETF activity,

That does _not_ require a photo.


>
> whether they are explicitly sign something,
> are photographed, are identified by RFID,

Keep in mind that if it isn't _voluntary_ consent, it will be legally
void, even with a signature on it.


>
> have their names written down after they say something at a microphone
> or on Jabber, raise their hands (presumably in the expectation of being
> identified), or can be identified in some other way.

What is wrong about simply archiving the information that participants
are providing voluntarily, such as it has been the last 20 years?


In Germany, an employer is not entitled to have and use a photo or picture
of an employee without explicit, voluntary and anytime revocable
consent of that employee (with very few and very narrow exceptions
carefully scoped by the legislator).  Writing something to a
different effect into the employment contract will be legally void,
because the consent to use the picture MUST be voluntary and
anytime revocable.


>
> Of course, an acceptable alternative to "no meetings in Germany
> or any other country with the rules you suggest apply" would be
> explicit permission on registration forms as a condition of
> attendance.  Or, presumably, a Chair could make an announcement
> that anyone who continues to sit in a particular room is giving
> permission for such identification.

Please do not confuse any necessity to identify an originator of a
contribution (which is where data protection laws would apply)
and the personal privacy rights of individuals about photos&portraits
of themselves.

-Martin