Re: Change in IPR policies

Jay Daley <jay@ietf.org> Tue, 09 June 2020 22:31 UTC

Return-Path: <jay@ietf.org>
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 E3B1E3A09A8; Tue, 9 Jun 2020 15:31:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=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 Z4IEX7sUmSjU; Tue, 9 Jun 2020 15:31:45 -0700 (PDT)
Received: from macbook-pro.localdomain (unknown [158.140.230.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 407483A0A93; Tue, 9 Jun 2020 15:31:45 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Subject: Re: Change in IPR policies
From: Jay Daley <jay@ietf.org>
In-Reply-To: <032e01d63ea7$534b4270$f9e1c750$@olddog.co.uk>
Date: Wed, 10 Jun 2020 10:31:43 +1200
Cc: trustees@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <859539A9-ACD2-4E69-8657-7D4A7FE899B6@ietf.org>
References: <96A3BDFE6F7DC38D2366581F@PSB> <45F719DA-115A-40C7-B96F-7F2D06E33199@ietf.org> <030e01d63e9f$9fcf3f50$df6dbdf0$@olddog.co.uk> <13080222-C9C3-44C6-B78C-AEE272639E51@ietf.org> <032e01d63ea7$534b4270$f9e1c750$@olddog.co.uk>
To: ietf <ietf@ietf.org>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xMoaLSjq30gxPK4cbqfjAMyJzlM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 09 Jun 2020 22:31:53 -0000

I have reviewed the checkbox presented during registration that says "I understand that I may not distribute or broadcast any electronic recordings of meeting events (including plenaries, tutorials, working group sessions, etc.) without IETF’s prior written consent" and this checkbox will now be removed.

I want to apologise first for the overly broad scope of that statement, which is on me for not reviewing it before it went up, and second for not recognising the impact of this on the general IPR policy.  While the former issue may be fixable, the latter is not and so the checkbox needs to go.

As explained, the original intent was to prohibit livestreaming, which in combination with open jabber rooms would enable people to participate in sessions without registration.  The concern there was not to protect the income stream from the meeting, but to ensure that we respect and recognise the decision of those people who register and pay by not allowing an obvious backdoor that avoids that.

The decision about the audio stream was slightly different.  I mistakenly thought that this was discontinued a while ago and so took the decision not to turn it back on just for this meeting.  I would prefer to stick with that decision given that Meetecho allows people to watch/list to multiple streams at once and the concerns I’ve expressed above.

I understand the view that we should be using an honor system and seeing if that fails us first, and that was considered but the risk of doing that was seen as too great.  First, I think we all recognise now that the honor system is much less effective online than in-person for a variety of reasons including low barriers, limited repercussions and effective anonymity, and so the likelihood of the honor system working is much less than in-person.  Second, the consequence of getting it wrong could have been a large number of people abusing that and those who didn’t abuse it feeling very aggrieved at us for allowing that.

I welcome any further feedback.

Jay

-- 
Jay Daley
IETF Executive Director
jay@ietf.org