Re: Video recordings

Christian Huitema <huitema@huitema.net> Thu, 05 June 2025 21:42 UTC

Return-Path: <huitema@huitema.net>
X-Original-To: ietf@mail2.ietf.org
Delivered-To: ietf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 67A243180B8B for <ietf@mail2.ietf.org>; Thu, 5 Jun 2025 14:42:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: 1.637
X-Spam-Level: *
X-Spam-Status: No, score=1.637 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SBL_CSS=3.335, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=mfg.outbound
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Oqe9CAyVWkn for <ietf@mail2.ietf.org>; Thu, 5 Jun 2025 14:42:41 -0700 (PDT)
Received: from semf07.mfg.siteprotect.com (semf07.mfg.siteprotect.com [64.26.60.170]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 9897D3180B88 for <ietf@ietf.org>; Thu, 5 Jun 2025 14:42:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mfg.outbound; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:Cc:From:References:To:Subject:MIME-Version:Date:Message-ID: reply-to:sender:bcc; bh=UQTGXV84QBs5U2ayoyMCsG8h463GVHxK3LZI7GIIqwY=; b=DAyr3 eRTpZsoc72v885NyRnxckay5VTD1drChYE+CQRm4d1angLPRXzbmykLIcxh9WdydfkyT3AzUP+T34 Gt54YNZ7Li92foFJYjnOV6NijYlUybJMthOA1RSX8CQ4C6LiYrnicm4vciWFTwkheiC3UdGzBGCbY x0AT510pafi9J0byqbzxwYJ4Vx/LDAkFjGlHRVoDQVp8+usK1Q0pFQpA3A2+9DdHVQxR7UhEUvZ9t V0X0oJjT6r9QbyhIYPaAyl/WihiNK/2W8sIQ4/D9rYjdbVGbg2JWv3w6HmihA28jgMnnysTg797Q6 kF/7Pvingn3LMYqrkXSLR6lmtMufw==;
Received: from smtpauth02.mfg.siteprotect.com ([64.26.60.151]) by se02.mfg.siteprotect.com with esmtp (Exim 4.94.2) (envelope-from <huitema@huitema.net>) id 1uNILz-003kfA-PF; Thu, 05 Jun 2025 17:42:40 -0400
Received: from [192.168.1.105] (unknown [172.56.170.224]) (Authenticated sender: huitema@huitema.net) by smtpauth02.mfg.siteprotect.com (Postfix) with ESMTPSA id 4bCybL6zzrzCSG1Ll; Thu, 5 Jun 2025 17:42:22 -0400 (EDT)
Message-ID: <398b9c59-eb5d-41ef-b26e-dcfdda25c34b@huitema.net>
Date: Thu, 05 Jun 2025 14:42:20 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Video recordings
To: ietf@ietf.org
References: <dcea4a2f-18f8-4feb-9891-a9482735c06b@nostrum.com> <c4f1c48adefefafeb4e39ff09d0a55a7b7bf55be.camel@fiebig.nl>
Content-Language: en-US
From: Christian Huitema <huitema@huitema.net>
In-Reply-To: <c4f1c48adefefafeb4e39ff09d0a55a7b7bf55be.camel@fiebig.nl>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Authentication-Results: mfg.siteprotect.com; auth=pass smtp.auth=huitema@huitema.net
X-Originating-IP: 64.26.60.151
X-SpamExperts-Domain: mfg.outbound
X-SpamExperts-Username: 64.26.60.150/31
Authentication-Results: mfg.siteprotect.com; auth=pass smtp.auth=64.26.60.150/31@mfg.outbound
X-SpamExperts-Outgoing-Class: ham
X-SpamExperts-Outgoing-Evidence: Combined (0.25)
X-Recommended-Action: accept
X-Filter-ID: 9kzQTOBWQUFZTohSKvQbgI7ZDo5ubYELi59AwcWUnuUcgyEQCYh4KUszzffQHuVPuayESoocC6pF TNcP9FB7XCu2SmbhJN1U9FKs8X3+Nt127hcteP1p0NVNV47moiZtUnZMMMyaNBeO+OvFQHUlG4JL M0i5ZAms0EHrvcCaVIP93FDv8fmm7aquK9rAkd8+GnT3EFAinyrilm9zau/FuzkQt9Nb4Ml7QXdk EetczWAP7aaIPrIjDj59Wk4xpVNfeB7itP8hgjDRserKv4bhb5ad32FAu+dBavD9Yzm05DvEMzer JfQa9UAYKsgEV8p+MUJTS2Jsxpkx+IHIsDarm2U3gyy0nlbakKK22WPBaizjKzb+JrnOTbl8FYp7 CIWjverajYy2yB71RZy29b9HL7yliuqXZvH3i216cQum165Jzwpab8TNaNA2TVJEVUqkCQjI0JpG 9Sl+IrgqZ8yCAf6BtLCA/2ZzeU/EVCt0iRqsFnrUFGVLXIAVOe7kb4yXabV6SPRLmlwlY38FC+ii 9DxIPj1UU4msT2Odp9D6f/OS6c4Ni1u8/va8CY7KOnP1w35D5h7lHy1+uoUhSMvvWxgWfVqs1QlX N1wi3QKSJb5OB2XvjaW5uTwPc8Wgwrru53p2681lMNl+tmUH3rQTflnesjcTklCLJhgiQ7kohkjS AIttXPEgCLSmIU9J1aqq/yJ79jYxxklvhfrt8SqXfz0JgYF1D/W5LWSzHwsmcAVCG4MYeONscQfo 5PBZrlL8zqUqLa6c4RN3CaQKGkBju2E7RErysG79fqF4kMNEV8K4LKK2owySnr2DLPb5g08vwR2R k4mrZetichC/8X2hN6U2/5iaqel3UlOHcLqhLjsE4mVK/YyYYCK2tZM8DmeaY7CEV13U061RTDB7 H8ExcSGvo+0yQ1haJlOk8imwNE0uDvHxUvKeKdTt6YNpe+8MctgzcDoFd+96Xw4QUNtTnWqZHG1f W6vvykF62wbG1JJ4HTvlNLDpwmANrq4YJD6zkJ2nOo9Yz9fp63maI2oeD8pQTeg1FsdCLj5jm+lJ mfSPSnixJZ2s/v8X3QUUfXRnZNh8ea17GeukGUZa3y8gfWu1/wl/f+Tjkn2bQ/A8pE7zyDpAeSJ7 eVNoxs/Ss/VLwGW5lrzMGGXQN6iDSOMnh0ZSTfwHmEIhU/ugYCTMkWs=
X-Report-Abuse-To: spam@se02.mfg.siteprotect.com
X-Complaints-To: abuse@se01.mfg.siteprotect.com
Message-ID-Hash: UBNO7X7K2OYHCIWXMQHQLFGOA7NWJAOA
X-Message-ID-Hash: UBNO7X7K2OYHCIWXMQHQLFGOA7NWJAOA
X-MailFrom: huitema@huitema.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: tobias@fiebig.nl
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PuRmNNmUD5VkwhRhz1s8E1THd_U>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>

On 6/3/2025 11:20 PM, Tobias Fiebig wrote:
> Moin,
>> We are (and have been for some time) looking for other streaming
>> solutions to use in addition to YouTube. [...]
>>
>>      We currently have between 300K and 400K minutes of video (around
>>      2.5TB) growing at about 60K minutes (300G) per year.
>
> So, some points for that:
>
> - I'd be happy to host a(n additional) mirror ftp/http for that; 2.5TB
>    with 300G growth does not sound too bad.
> - Streaming-site wise, it might make sense to reach out to the
>    VOC / media.ccc.de; There might be some opportunity there to join
>    forces. If you want, I can see whether I can make a contact.

I am trying to explore how we could set up a peertube server to present 
IETF videos. As Antoine Fressancourt previously mentioned, peertube is 
an open source standard, supporting ActivityPub and thus integrated in 
the Fediverse. People more knowledgeable than me have assured me that 
hosting the IETF videos would be easy, and a couple of them have 
proposed using their own servers. But I wanted to learn a bit more 
before being able to present the results to the tool teams.

My first todo item was to estimate the load. Robert Spark answered that. 
Getting 2.5TB of storage and adding 300G per year is not extraordinary. 
It probably requires a dedicated server. Serving 600K minutes per year 
is also not too extraordinary, but probably requires a bit of planning. 
According to https://joinpeertube.org/en_US, peertube has built in 
provisions to offload part of the traffic. If that does not suffice, 
some CDN support might be required.

Second item on my list was understanding how the data can be uploaded 
from the IETF to a peertube server. I assume the tools team has 
something available.

The third item is to do a little experiment. Any final solution would 
have to be IETF branded, probably registering the a server name under 
ietf.org. But before that we can set up a peertube server with a small 
subset of the video, and assess how it works. Mainly, check that the 
upload process can run smoothly, and that the user experience is good. 
We are not there yet, but could do that very soon once we understand how 
to upload videos. Once we have done the experiment, we will know whether 
peertube would be an OK solution.

We may be able to get some results before the June 10 meeting of the 
tools team, but they would be preliminary. I thought it would be a good 
idea to discuss this peertube option at a side meeting during the next 
IETF.

Any suggestions about next steps? Maybe set up a mailing list, organize 
a side meeting, work with the managers of peertube servers who already 
volunteered?

-- Christian Huitema