Re: Change in IPR policies

Russ Housley <housley@vigilsec.com> Tue, 09 June 2020 20:29 UTC

Return-Path: <housley@vigilsec.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 90E9F3A0889 for <ietf@ietfa.amsl.com>; Tue, 9 Jun 2020 13:29:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 N14IfzP9tIIX for <ietf@ietfa.amsl.com>; Tue, 9 Jun 2020 13:29:33 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6A413A0870 for <ietf@ietf.org>; Tue, 9 Jun 2020 13:29:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 4471A300B6E for <ietf@ietf.org>; Tue, 9 Jun 2020 16:29:31 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id SZoFm-fdbeRV for <ietf@ietf.org>; Tue, 9 Jun 2020 16:29:29 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (pool-72-66-113-56.washdc.fios.verizon.net [72.66.113.56]) by mail.smeinc.net (Postfix) with ESMTPSA id 80FBF300A31; Tue, 9 Jun 2020 16:29:29 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <84C753E2-9C55-4ACC-8741-EB952B57F590@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_75039B8E-25EA-4CB1-8A90-B18559F8DDFA"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Subject: Re: Change in IPR policies
Date: Tue, 9 Jun 2020 16:29:30 -0400
In-Reply-To: <96A3BDFE6F7DC38D2366581F@PSB>
Cc: IETF Trustees <trustees@ietf.org>
To: IETF <ietf@ietf.org>
References: <96A3BDFE6F7DC38D2366581F@PSB>
X-Mailer: Apple Mail (2.3445.104.14)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/okcpQXZYMJyEI-2wKsdjOWOcko0>
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 20:29:42 -0000

> (2) There is a very specific and, as far as I know, completely
> new, prohibition against distribution or broadcasting of any
> meeting-related discussion or events.  That seems like a giant
> step away from the IETF's tradition of openness and free
> availability of materials. 

The IETF makes the recording of the meeting available on youtube.  For example: https://www.youtube.com/watch?v=ti2iE0jBL0s <https://www.youtube.com/watch?v=ti2iE0jBL0s>

Like John, I'd really like to understand why this check box was added to the registration, especially without prior discussion.  I do not believe that the IETF Trust is claiming any copyright on these recordings.  If the IETF Trust is about to do so, that is a huge change in policy that requires advanced discussion.

Russ