[Tools-discuss] Closure (was Re: Reminder (Re: [Manycouches] Proposal to discontinue live mp3 audio streams at IETF meetings))

Robert Sparks <rjsparks@nostrum.com> Tue, 20 October 2020 19:07 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC4313A1301; Tue, 20 Oct 2020 12:07:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.403
X-Spam-Level:
X-Spam-Status: No, score=-1.403 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.275, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 705PhCJtPh9V; Tue, 20 Oct 2020 12:07:52 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 105023A0A7B; Tue, 20 Oct 2020 12:07:51 -0700 (PDT)
Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 09KJ7hXf032834 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 20 Oct 2020 14:07:44 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1603220865; bh=ylCsHnVHB2453nKfnqzz8rl4Gc+WMzyxuOCVX5SQboM=; h=Subject:From:To:Cc:References:Date:In-Reply-To; b=QJax1MY+1H5aGw8rKvJqw2/T3T/pwVth9fc8RJnMmwIa9P644ZlDEd/YpFMTiKFCo ypVDYM6G0emf0go3rmgcJz/qeL/uzBrpSdWVjwuJw4k3NLR1I3/Fi5gWxg2r08GC1/ vDO+GhzBkG8I1mp5dwWE+DMeLs0kxBfpf9yU8TtI=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local
From: Robert Sparks <rjsparks@nostrum.com>
To: Tom Pusateri <pusateri@bangj.com>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: Carsten Bormann <cabo@tzi.org>, Tools Discussion <Tools-discuss@ietf.org>, manycouches@ietf.org
References: <137438FD-E3FC-40C3-B482-B0E555F5318B@tzi.org> <CA9F75B2-2709-4619-8E64-845F1DFC826C@bangj.com> <743e6bef-ba4b-db2f-1980-62f967560924@nostrum.com> <c2b71e2f-7f1d-b2f9-ace4-73a82dc30e01@gmail.com> <622776EA-0F69-4B28-9CD2-D099EBB8D1DD@bangj.com> <63a1fb8c-12eb-a8e7-7bd0-1676d7dbb394@nostrum.com> <cb6aeba8-32b7-d42d-e6bf-e00ad6c46da5@nostrum.com>
Message-ID: <b774eba9-014c-7dab-6d40-8e9c63f0c266@nostrum.com>
Date: Tue, 20 Oct 2020 14:07:43 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0) Gecko/20100101 Thunderbird/78.3.3
MIME-Version: 1.0
In-Reply-To: <cb6aeba8-32b7-d42d-e6bf-e00ad6c46da5@nostrum.com>
Content-Type: multipart/alternative; boundary="------------79767B8E0C4556C5615382FD"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/XMPHr428FormUamiGVd3Xm_bnGY>
Subject: [Tools-discuss] Closure (was Re: Reminder (Re: [Manycouches] Proposal to discontinue live mp3 audio streams at IETF meetings))
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2020 19:07:54 -0000

I have not seen any further responses.

We will do the retooling needed to provide live audio streams as one 
named stream per session.

RjS

On 10/14/20 10:23 AM, Robert Sparks wrote:
>
> (With apologies for the intentional crosspost)
>
> If you have more to say, please do so by 16 Oct.
>
> My read of the feedback so far is that the evidence we had for low 
> usage was probably misleading, and there is still a demand for a live 
> audio stream if it were presented in a more useful form. I anticipate 
> we will do the retooling to provide these as one named stream per 
> session going forward. If anyone thinks that is not what we should be 
> doing, please say so.
>
> RjS
>
>
>> We propose to discontinue producing live mp3 audio streams for IETF 
>> meetings,
>> starting with IETF 109 and we want to hear from the community before 
>> we do.
>>
>> At many past meetings we have produced live mp3 streams for each 
>> session. These
>> steams have been associated with physical meeting rooms, and appeared 
>> before
>> and during the session as a link on the agenda page to a URL like
>> 'http://mp3.conf.meetecho.com/ietf/ietf<some_number_associated_with_the_room>.m3u'. 
>>
>>
>> For the last several meetings, these have only been available as a 
>> live stream.
>> Recordings of that stream have not been made available after the 
>> meeting. The
>> full video recording provided by Meetecho has served as the way to 
>> listen to
>> (or watch) any given session after the fact.
>>
>> Further, for the last several meetings, the live streams have seen 
>> very light
>> use, on the order of 10 uses for IETF 108.
>>
>> Now that we are holding more meetings online, we have a requirement 
>> to allow
>> meetings to run outside their scheduled times. Allowing the live 
>> streams to run
>> outside their scheduled times will require changing how they are 
>> represented,
>> to no longer be associated with "rooms" or "tracks". The code 
>> refactor at both
>> the datatracker and at meetecho to support would not be a huge 
>> effort, but it
>> also would not be tiny. Instead, we feel that removing this complexity,
>> recognizing that the regular meetecho connection and recordings 
>> satisfy the
>> need, is the better use of our resources. That holds true even for 
>> future
>> in-person meetings.
>>
>> There are several points that have been considered while arriving at 
>> this
>> proposal:
>>
>> * Chairs use the recordings to fill in minutes.
>>
>>     For the last several meetings, the chairs have been using the 
>> Meetecho
>>     recordings for this purpose. Recordings of the live mp3 streams 
>> haven't
>>     been available.
>>
>> * Some participants (especially ADs) want to listen to more than one 
>> meeting at
>>   a time.
>>
>>     Meetecho allows joining multiple sessions.
>>
>> * Some participants may not have the bandwidth or a new enough 
>> computer to run
>>   meetecho.
>>
>>     The use of the mp3 streams has been very low at the last several 
>> meetings.
>>     This population isn't using the mp3 streams to address the posited
>>     limitations.  If this is a     concern that some people think 
>> they will
>>     experience then we can look at asking Meetecho to allow sending only
>>     audio (muting all video).
>>
>> * This removes a mechanism that allowed people to listen to a session in
>>   real-time without paying a registration fee.
>>
>>    There will be ongoing discussion and tuning of the meeting 
>> registration
>>    structure. In the meantime, the fee waiver program is available 
>> and being
>>    improved.
>>
>> Please send comments by 16 Oct 2020 either to tools-discuss@ietf.org or
>> directly to rjsparks@nostrum.com.
>>
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>