Re: IETF note well relating to pictures?

Joe Hildebrand <hildjj@cursive.net> Wed, 27 July 2016 16:28 UTC

Return-Path: <hildjj@cursive.net>
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 A255512B03C for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2016 09:28:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.49
X-Spam-Level:
X-Spam-Status: No, score=-2.49 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_LOW=-0.7, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=cursive.net
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 IYq0nlROwcGr for <ietf@ietfa.amsl.com>; Wed, 27 Jul 2016 09:28:53 -0700 (PDT)
Received: from mail-pf0-x233.google.com (mail-pf0-x233.google.com [IPv6:2607:f8b0:400e:c00::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16ADC126FDC for <ietf@ietf.org>; Wed, 27 Jul 2016 09:28:53 -0700 (PDT)
Received: by mail-pf0-x233.google.com with SMTP id x72so12453048pfd.2 for <ietf@ietf.org>; Wed, 27 Jul 2016 09:28:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cursive.net; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=BMgx57UdSG5O2il7bSeaakG6VebfAqJKSFRtcSYFDx0=; b=K2Sn4hpvn3zsVQq8DxU7h14Wu9VWEu7gnQ2SHlbnl3PUOFxZMUnolhmdSDIKXQ0JzP EaTtN4Z4/bPRtnxXgvFdTWOJO76Nw9ocaVFwNwc0dfEBPTegA5MH1v6w5Wx14mRp/Sq8 cYXrbyCjGHRJkKjuV0z9eBJmO2cp6wHlexNnY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=BMgx57UdSG5O2il7bSeaakG6VebfAqJKSFRtcSYFDx0=; b=OTBt+w12CL1Tmzhsf2bzLOEOl9JLwXejCk89f8oGIqB/1EMGXWHYbMekrtugUUGtOM 2gw7GDSW/CZKVYoWsGrTKQudvr3xODwXfU94Q4lNng9BOGEEQafr1a/R+/ZrdhuLkLVm ACvgBsC7kccLE7QykjvmHXeKtvZLjXL41IFohOckkwBbbRJkEbcCFfUfoXnm4sXcT19D mcAfSaNPcOXklgNuI9R26esqGOiHcmqu+CirYbboVDajSrYNm8l17t9csgSi8nfnIHt/ 7+9yHWTdKxeB+V/DebfwUQSnf89vsZq+ljYEQ4fg1DTQeR3gIlcikpmn+qOGXdTqB4/P DsIg==
X-Gm-Message-State: AEkoousDaS0+KoeokWgM7dg8Sd9SkMvcXsrK0/b1R0ty/sR9E7egSpmDWg4oUA5PiffFHA==
X-Received: by 10.98.201.138 with SMTP id l10mr50865310pfk.77.1469636932631; Wed, 27 Jul 2016 09:28:52 -0700 (PDT)
Received: from sjc-jhildebr-nitro8.cisco.com ([128.107.241.175]) by smtp.gmail.com with ESMTPSA id ao6sm6767476pac.8.2016.07.27.09.28.51 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 27 Jul 2016 09:28:51 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: IETF note well relating to pictures?
From: Joe Hildebrand <hildjj@cursive.net>
In-Reply-To: <CAA=duU2kV07aWk9CvnP4QA=8nynNS+bb23nCxNgJa3ut-be+eg@mail.gmail.com>
Date: Wed, 27 Jul 2016 10:28:50 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <652129DE-18F3-4B17-9F67-6322B51E7CDA@cursive.net>
References: <CAF4+nEHWP3k+2ikrpByVoEXwf0Rp7BuLAqTnk7n+aKxEQX3ZGg@mail.gmail.com> <20160726105626.881741A508@ld9781.wdf.sap.corp> <6.2.5.6.2.20160726230853.0ab08708@resistor.net> <CAA=duU2kV07aWk9CvnP4QA=8nynNS+bb23nCxNgJa3ut-be+eg@mail.gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/r3iVKT_ReN91t9GTfZh6Py1LsiE>
Cc: S Moonesamy <sm+ietf@elandsys.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
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: Wed, 27 Jul 2016 16:28:57 -0000

Some conferences are using colored lanyards as a way for people to declare their preferences proactively:

https://adainitiative.org/2013/07/04/another-way-to-attract-women-to-conferences-photography-policies/

Personally, I would likely wear a red lanyard (photographs never okay, don’t ask) unless I'm on stage, presiding, or presenting (when I would take off the lanyard).



> On Jul 27, 2016, at 6:23 AM, Andrew G. Malis <agmalis@gmail.com> wrote:
> 
> Here’s a concrete example. Photos of IETF plenaries have been published, online or otherwise, in various formats and venues, such as on Facebook or on blogs. Sometimes I’ve spotted myself in the photos, in at least one case very visibly. However, it is impratical to check with every single person attending the plenary to ask their permission ot publish the photos. Should they be allowed to be published? I think so, even though I wasn’t asked at the time.
> 
> Cheers,
> Andy
> 
> 
> On Wed, Jul 27, 2016 at 3:12 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:
> Hi Martin,
> At 03:56 26-07-2016, Martin Rex wrote:
> The issue isn't about recording, but about publication.
> 
> And you really need _consent_, any rip-off/coercion in the US contractual
> style (package deal) will not work here, because such contract clauses
> will be legally void in Germany, similar to most of the contents of
> click-through-licenses in software.
> 
> The issue is much less about folks on stage, but folks in the room
> -- an that is what the original question was about.
> 
> The original question was about about whether it is okay to publish pictures of a person for just being on the premises.  The short answer is that the photographer could ask the person whether he/she is okay with having his/her photo taken.
> 
> The Note Well is about activities such as working group sessions or a plenary [1].  The question here would be about whether it is appropriate for the organization to publish audio/video recordings of those activities.  That would be covered by a privacy policy.  There isn't a simple answer as each country has its own laws.  The discussion about what is public highlights the differences.
> 
> Regards,
> S. Moonesamy
> 
> 1. There have been discussions about other events in respect to Contributions. 
> 

-- 
Joe Hildebrand