Proposed Photography Policy

Eric Rescorla <ekr@rtfm.com> Fri, 02 March 2018 04:02 UTC

Return-Path: <ekr@rtfm.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 B9D59126C19 for <ietf@ietfa.amsl.com>; Thu, 1 Mar 2018 20:02:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.639
X-Spam-Level:
X-Spam-Status: No, score=-1.639 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
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 mgKmastoOE1H for <ietf@ietfa.amsl.com>; Thu, 1 Mar 2018 20:02:17 -0800 (PST)
Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::234]) (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 85793124D68 for <ietf@ietf.org>; Thu, 1 Mar 2018 20:02:17 -0800 (PST)
Received: by mail-qt0-x234.google.com with SMTP id v90so10410770qte.12 for <ietf@ietf.org>; Thu, 01 Mar 2018 20:02:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=IgD4A452ahVq22PF8g/DEQQhXQSgJRgaAvR6qOwoJNU=; b=XnqMi9CER6dSi9nrV6r7YRvPFoWLO1AzhppT8XRLXpowufh7tDqmPUBEBB2CNx0RBS 0Z77aTV04kSQ/rhopxZMNc+OMkUp+ybQZrxvHBc5b55EgW2F2cwu8E5gKRfb4/H6rR2O pbvLSfEFSAHAUiQvJjlHMk++KCbSAa2R659hCQe0lt/KPcZ4nFIKpOj4xvc0LJGGlW+c 0T4gClssv8WzThlTWnHygouuVGyidEUvVsFIbGA71Pi7vpIwTHNoNsTg3wDlbJW4+z/A PFy0H9NL9Oip+n/z3Vj2ohEfBj1vfOfPRpp6p0s/f9QDQQTY+4JfwgJhsdMPVhnnzKa3 8sNw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=IgD4A452ahVq22PF8g/DEQQhXQSgJRgaAvR6qOwoJNU=; b=KF+3HynbW08wKwk1TYKbCVxMaEEFBK65W+/02N0PAslLKUzGL5c6POV5ds024opGeH gJ4bm6IncU45dzRD2B368JNvWeNRk/f72vSHU7DRxSZtevyKuIIhb81btcBXanyFXX65 2aIfVljuMN778c33ZGyIFz2U/DhhlOooffKSv+KXljAZzt8BonDvv+9HgPT760qUdaVI XlLiAINyg+G91AY+CixSZmuV+R8iwx/aCiiTXtHedfwHHH2osPWcYVaEV5+E6e8pw32Z 0FNivtv1NxSe6fiqkaD0sanWjTi9YhloTVkl2C9xUQyTIIJ+1NMGkHozp1mMfFg3IHDN InQw==
X-Gm-Message-State: AElRT7HBXmW9/ROBRdA74MKoFXQvzDmZ4UcvhoykEYFFPefZScxzHv4a SIeNAH3FkNCWyWU7AZ/1McJDXffTZI2umaVMwhL8CzqJkJ8=
X-Google-Smtp-Source: AG47ELuR8N1sHHxTJ3dOi5kdJYHYMbY0RRhcdCwmAquRKW+i7XetTnShFA3BuAP59eM9NTtlesUY5RimdqPvq/M+Ack=
X-Received: by 10.237.32.135 with SMTP id 7mr6545426qtb.287.1519963336322; Thu, 01 Mar 2018 20:02:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.200.37.176 with HTTP; Thu, 1 Mar 2018 20:01:35 -0800 (PST)
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 01 Mar 2018 20:01:35 -0800
Message-ID: <CABcZeBMtorh-kRX2pDWY2ws4w4sNKPzMdaA=CaA0ukKxYwSf-A@mail.gmail.com>
Subject: Proposed Photography Policy
To: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c114ed0bbccec0566660ad1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Qz6UNZ-7jBgK_KKu7mSgvi89GdE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 02 Mar 2018 04:02:19 -0000

Hi folks,

The IESG has heard some concerns from participants that they would like
not to be photographed. In response to those concerns, we have developed
the attached policy which we intend to put in place going forward.

Please send any comments by 3/8/2018.

-Ekr


-----
The intent behind this policy is to balance people's legitimate desire
not to be photographed with the IETF's ability to document activities
and enable remote participation. In order to enable that, we are
proposing the following policy which applies to all IETF events,
including WG meetings, plenaries, and the hackathon.

LABELLING
The IETF will make available a mechanism for participants to label
themselves as desiring not to be photographed. The secretariat will
determine the details in consultation with the IESG.

OFFICIAL PHOTOGRAPHY
Any photographer engaged on behalf of the IETF should not photograph
 individuals
displaying the "do-not-photograph" label, should make reasonable
efforts to avoid photographing small groups with one or more members
displaying the label, and should not publish small group photographs
with such individuals in them. Photographs of large groups may contain
incidental images of such individuals and we will not attempt to
redact those. Specifically, photographs of panels and the like (e.g.,
the IESG/IAB plenary) are expected to contain all individuals
regardless of labelling.

Working group meetings are generally video recorded and broadcast, and
no attempt will be made to avoid recording individuals. However, if
the IETF publishes still frames of these videos, individuals
displaying the labels should not be shown.

Note: the use of "should" above is intended to reflect that although
this is IETF policy, it is a best effort service and some mistakes
will likely be made, perhaps because someone's label is not noticed or
visible. Individuals can contact XXX to arrange for redaction of their
images, or YYY to report abuse.


UNOFFICIAL PHOTOGRAPHY
Many IETF participants also engage in photography. We ask that those
participants respect the above policies and avoid photographing
individuals who have asked not to be photographed. Although we
recognize that mistakes will be made, repeated intentional violations
of this policy may constitute harassment and could be brought to the
attention
of the ombudsteam, per RFC 7776.