IETF Logo Mail Archive

Re: Video recordings

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 06 June 2025 13:21 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 2735331C5660 for <ietf@mail2.ietf.org>; Fri, 6 Jun 2025 06:21:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.4
X-Spam-Level:
X-Spam-Status: No, score=-4.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 6drrBggcSL3o for <ietf@mail2.ietf.org>; Fri, 6 Jun 2025 06:21:01 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (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 C65FD31C565B for <ietf@ietf.org>; Fri, 6 Jun 2025 06:21:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 3A6B71800E; Fri, 6 Jun 2025 09:21:01 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id lMu7qW605mtc; Fri, 6 Jun 2025 09:20:59 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1749216059; bh=xY1sZftvwFBFhbovAvIvfxRQRbLALP0EY4u3C4+H+vo=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=uBrWAQXRiHvNmpdYhszTUTaacS6mrS1V4Z3j+S6iAcbnf4UZTai0Q/vJOvIU2llKc mKkXOXfcFre6YKJW7c5hbHHuIvn9hhJF/1ryYKWLpda0BVlBljRE8A3ZqHx4wh/1NG 0SxYAn7/aLHt8NvmveHEm0WaG5fQCFc6wAIJWAiM8zoXBtlBHUKwY5USUfA9V2ODFF rNhazhRRb3tHd434Icersg2GKfkEtrzr6pfGEAa0w1aE5baPFJrCfTUE+xkrjhLqyO kUfcQf/pu4kodsbIXVeEGdj/sgQEJA4wp1fGw5P8ijJha1qRiktUE2yVNM6QIh5Bk2 I1jCM4oSsadug==
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:4c22:dbff:fefd:1b86]) by tuna.sandelman.ca (Postfix) with ESMTP id 721951800C; Fri, 6 Jun 2025 09:20:59 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 4155818E; Fri, 6 Jun 2025 09:20:54 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Christian Huitema <huitema@huitema.net>
Subject: Re: Video recordings
In-Reply-To: <398b9c59-eb5d-41ef-b26e-dcfdda25c34b@huitema.net>
References: <dcea4a2f-18f8-4feb-9891-a9482735c06b@nostrum.com> <c4f1c48adefefafeb4e39ff09d0a55a7b7bf55be.camel@fiebig.nl> <398b9c59-eb5d-41ef-b26e-dcfdda25c34b@huitema.net>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; GNU Emacs 28.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 06 Jun 2025 09:20:54 -0400
Message-ID: <1321606.1749216054@obiwan.sandelman.ca>
Message-ID-Hash: I47BG4NJBQ2VT3UNOHJYFKKH2FBTTBOU
X-Message-ID-Hash: I47BG4NJBQ2VT3UNOHJYFKKH2FBTTBOU
X-MailFrom: mcr+ietf@sandelman.ca
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: ietf@ietf.org, 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/bTYu_sNJi7cYK1nSCjPtpT-Un9Q>
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>

Christian Huitema <huitema@huitema.net> wrote:
    > I am trying to explore how we could set up a peertube server to present
    > IETF videos. As Antoine Fressancourt previously mentioned, peertube is

Thank for leading this.

    > 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

I don't know how to convert 600K minutes/year into bits/second.
But, assuming people watch for only 250 days/year (M-F), then that's 2400
minutes of video per day, or 100 minutes per hour.  That's ~ two streams
flowing at any one time.   Peak could be significantly higher.

    > 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.

Good.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.35.0 | Report a Bug | By Email | System Status