RE: Change in IPR policies

Adrian Farrel <adrian@olddog.co.uk> Tue, 09 June 2020 21:45 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 33E373A0938; Tue, 9 Jun 2020 14:45:48 -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 R3fiWMcDdRv2; Tue, 9 Jun 2020 14:45:46 -0700 (PDT)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (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 2B95A3A0028; Tue, 9 Jun 2020 14:45:46 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta7.iomartmail.com (8.14.4/8.14.4) with ESMTP id 059Lji5X029125; Tue, 9 Jun 2020 22:45:44 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 5FB5B2203B; Tue, 9 Jun 2020 22:45:44 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs1.iomartmail.com (Postfix) with ESMTPS id 49D222203A; Tue, 9 Jun 2020 22:45:44 +0100 (BST)
Received: from LAPTOPK7AS653V ([84.93.26.18]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id 059Ljgkb011216 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 9 Jun 2020 22:45:43 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Jay Daley'" <jay@ietf.org>
Cc: "'John C Klensin'" <john-ietf@jck.com>, <trustees@ietf.org>, <ietf@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>
In-Reply-To: <13080222-C9C3-44C6-B78C-AEE272639E51@ietf.org>
Subject: RE: Change in IPR policies
Date: Tue, 9 Jun 2020 22:45:40 +0100
Organization: Old Dog Consulting
Message-ID: <032e01d63ea7$534b4270$f9e1c750$@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+KGAJJJVu8AcZhXHkCaWXuhaiR0iTw
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.003
X-TM-AS-Result: No--5.204-10.0-31-10
X-imss-scan-details: No--5.204-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25472.003
X-TMASE-Result: 10--5.204400-10.000000
X-TMASE-MatchedRID: xcONGPdDH5rxIbpQ8BhdbPHkpkyUphL9BGvINcfHqhf0nlq8x3d7MFXa 1b4xhOVh8MqJaO20m/xgSTW/PZjcAYZzHzkb63hjGAZMT5SLmAkXyU2Cxtlxb7pH5/7OrnyGvCw D/MFgPQ6adWhX7h3NcxRzgoz8Iobckk1B+xxDSja1vYjMdtgWT8o0g7hj5evQBCzD0Dc8iUue8s gsK/PKtTnM+yGtLvc7hjDozoufp6UhLhpRWvILwedUdcFTNW9kUcH09qBGmHSZt08TfNy6OKwcW KwdSBcTPPvnIXb/+Vj78ZiX3vVqi7bN6KdkLSmKZ93oz43dfXFzWwGH37l9gyOWfE4h4x8wSHgU VMoIv2FTq4o4bP/HJumdIFGMTlHtTUKyAuqgJVp/n3z4qeww6H316REeU5CRmXw0RNbqkoKby9F 6QvnXNkEpAL8KZNCm0kdqLoZ8YVW/WXZS/HqJ2lOm2gN+nomsxEHRux+uk8h+ICquNi0WJPO1bO ONriQadlIbtgxzuFgrEAWJTArO8sala3909tLTftwZ3X11IV0=
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/-tVKkeuIxeMJkbhZ1VumfEinW40>
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 21:45:48 -0000

Hello again,

>> - The check box says "without IETF’s prior written consent"
>> so perhaps the IETF would care to grant that wholesale
>> and now.
>
> As I said, I will get that corrected.

Thanks. I'll wait to see that before commenting further.

>>- 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.)
>
> Audio streaming is not supported for the same reason that audio
> streaming + open jabber rooms effectively allows participation
> without registration.
>
> The platform for IETF 108 will be Meetecho not WebEx

My mistake.

> do you have the same concerns with that or are your concerns
> more generally about people participating from places where
> the cost of bandwidth is an issue for video?

I am not limited to one concern 😊

However, what I was asking about was:

1. Can I run multiple streams at once on one laptop (without setting up multiple VMs)? I suspect that I can do this with Meetecho, but I'd like to know for sure that the technology will support it and there won't be any gates that prevent my magic registration ID being in two parallel sessions at the same time.

2. Are there any assumptions about the platform that a user must have access to in order to run Meetecho and so participate? In particular, have we raised the bar to participation over simple audio streaming?

Appreciate what you're doing to try to sort all of this out.

Best,
Adrian