IETF Logo Mail Archive

Re: IETF note well relating to pictures?

mrex@sap.com (Martin Rex) Mon, 25 July 2016 17:11 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 7204312D915 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2016 10:11:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.922
X-Spam-Level:
X-Spam-Status: No, score=-6.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ajs8FMP8AoH8 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2016 10:11:08 -0700 (PDT)
Received: from smtpde01.smtp.sap-ag.de (smtpde01.smtp.sap-ag.de [155.56.68.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96C5812D508 for <ietf@ietf.org>; Mon, 25 Jul 2016 10:11:08 -0700 (PDT)
Received: from mail06.wdf.sap.corp (mail06.sap.corp [194.39.131.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtpde01.smtp.sap-ag.de (Postfix) with ESMTPS id 3rynpL0wDLz1Hlh; Mon, 25 Jul 2016 19:11:06 +0200 (CEST)
X-purgate-ID: 152705::1469466666-00000827-DF885A16/0/0
X-purgate-size: 964
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate-type: clean
X-SAP-SPAM-Status: clean
Received: from ld9781.wdf.sap.corp (ld9781.wdf.sap.corp [10.21.82.193]) by mail06.wdf.sap.corp (Postfix) with ESMTP id 3rynpK2f2xzkynv; Mon, 25 Jul 2016 19:11:05 +0200 (CEST)
Received: by ld9781.wdf.sap.corp (Postfix, from userid 10159) id 54B241A508; Mon, 25 Jul 2016 19:11:05 +0200 (CEST)
Subject: Re: IETF note well relating to pictures?
In-Reply-To: <e399d18d-974b-2547-d9fd-e06429f3a12c@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Mon, 25 Jul 2016 19:11:05 +0200
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20160725171105.54B241A508@ld9781.wdf.sap.corp>
From: mrex@sap.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DbEE9dM0BoF4XiGHHmWKdjwga8M>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Jul 2016 17:11:10 -0000

Brian E Carpenter wrote:
>
> "A participant in any IETF activity acknowledges that written,
> audio and video records of meetings may be made and may be
> available to the public."
> 
> I've always assumed that "video" includes still photographs.

Since this IETF happened in Germany, the local applicable on personality
right apply, and Note Well can not limit these personality rights.


https://www.gesetze-im-internet.de/kunsturhg/__23.html

https://www.gesetze-im-internet.de/kunsturhg/__22.html


While there are certain exemptions, the photographers that intend to
publish photos have to take into account the individual rights of the
persons on the picture, and they're strongly urged to ask for permission
rather than erroneously assuming that publication was generally allowed.

The rule is that publication requires consent of the people on the photos,
unless the _narrow_ defintion of one of the exemptions is met.


-Martin

v2.23.0 | Report a Bug | By Email