RE: Change in IPR policies

Adrian Farrel <adrian@olddog.co.uk> Tue, 09 June 2020 20:50 UTC

Return-Path: <adrian@olddog.co.uk>
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 C56253A0867; Tue, 9 Jun 2020 13:50:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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 kngRuQHac0Wl; Tue, 9 Jun 2020 13:50:39 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83A683A0865; Tue, 9 Jun 2020 13:50:39 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta6.iomartmail.com (8.14.4/8.14.4) with ESMTP id 059Koao7019898; Tue, 9 Jun 2020 21:50:37 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id D09D72203A; Tue, 9 Jun 2020 21:50:36 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs3.iomartmail.com (Postfix) with ESMTPS id BB60822032; Tue, 9 Jun 2020 21:50:36 +0100 (BST)
Received: from LAPTOPK7AS653V ([84.93.26.18]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id 059KoZLs015532 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 9 Jun 2020 21:50:36 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Jay Daley'" <jay@ietf.org>, "'John C Klensin'" <john-ietf@jck.com>
Cc: <trustees@ietf.org>, <ietf@ietf.org>
References: <96A3BDFE6F7DC38D2366581F@PSB> <45F719DA-115A-40C7-B96F-7F2D06E33199@ietf.org>
In-Reply-To: <45F719DA-115A-40C7-B96F-7F2D06E33199@ietf.org>
Subject: RE: Change in IPR policies
Date: Tue, 9 Jun 2020 21:50:34 +0100
Organization: Old Dog Consulting
Message-ID: <030e01d63e9f$9fcf3f50$df6dbdf0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHb2XMgRa+M4+Gd9co1ZdSHa5+KGAJJJVu8qLNBm8A=
Content-Language: en-gb
X-Originating-IP: 84.93.26.18
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25472.002
X-TM-AS-Result: No--5.141-10.0-31-10
X-imss-scan-details: No--5.141-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25472.002
X-TMASE-Result: 10--5.141200-10.000000
X-TMASE-MatchedRID: +f/wAVSGjujxIbpQ8BhdbPHkpkyUphL9B4Id7CiQcz9+SLLtNOiBhvyJ aFJtckS0qUOjBkkLxgEI8eUQMLlIpblppeG/cvfmtKV49RpAH3u6hgVvSdGKo/UnpN1C2hZ8dYJ 3pC9XNt6JK2sn9oIdznWxJczm65yEigGMSLL+p0uOjIrMSa2sR8CpG6QaSSlCcJHSK1bfF9W4KN oeDfLV7G8C2psaP3qCfrXMSJZxoXXE23SQ1uKiHqCS5FukbuIIb/gdKMAFtwaEAZ+8YfT0PaSLK JxuiASSW4rWWYOHc24TmCRJrPNaSVTNH/IEdCNmWBSfJTziFx+6s6UL48vRAINSdfAQYTpko8WM kQWv6iXh7z8MHC5cZ3QdJ7XfU86eOwBXM346/+x036lWi15KZbPd2DchglEqYgvgAxBbDZjSau3 1jdmHIRqH7WNxXyOo
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/g1vi94yoROquyIJld0kl7pPkD9c>
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:50: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.
>
> I need to check, but I think the intent there was to restrict 
> livestreaming and nothing else as the combination of live
> streaming + open jabber rooms would effectively allow
> participation without registration.  Once I’ve reviewed I
> will get that corrected.

Two points:
- The check box says "without IETF’s prior written consent"
  so perhaps the IETF would care to grant that wholesale
  and now.
- Does this mean that audio streaming will no longer happen?
   If so, I really (really, really) hope that Webex is going to let me
   join multiple simultaneous meetings so that I can easily skip in
   and out of the audio when I have an agenda clash. (I do also 
   wonder, in this case, how we support people with platforms 
   that can't run Webex in any of its forms.)

Best,
Adrian