[icnrg] low-latency and scalable video distribution

Dirk Kutscher <ietf@dkutscher.net> Wed, 23 March 2022 10:19 UTC

Return-Path: <ietf@dkutscher.net>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF32B3A0ED1 for <icnrg@ietfa.amsl.com>; Wed, 23 Mar 2022 03:19:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 jztUYji8LlKu for <icnrg@ietfa.amsl.com>; Wed, 23 Mar 2022 03:19:53 -0700 (PDT)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.187]) (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 E8DB93A0D53 for <icnrg@irtf.org>; Wed, 23 Mar 2022 03:19:52 -0700 (PDT)
Received: from [192.168.1.50] ([95.89.114.110]) by mrelayeu.kundenserver.de (mreue012 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MCGag-1nNaRI0tso-009RlK for <icnrg@irtf.org>; Wed, 23 Mar 2022 11:19:50 +0100
From: Dirk Kutscher <ietf@dkutscher.net>
To: ICNRG <icnrg@irtf.org>
Date: Wed, 23 Mar 2022 11:19:48 +0100
X-Mailer: MailMate (1.14r5852)
Message-ID: <0E9B8F59-42EE-4BA0-B04D-E9A0A042CA06@dkutscher.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_969145F0-5CA1-4DF2-A861-B7F0712D80E8_="; micalg="pgp-sha1"; protocol="application/pgp-signature"
X-Provags-ID: V03:K1:ZcOr5QnkVLVa1jyKGaSPlEBvPJISW2oWNRT8eF9YeT9Ofg6rr69 xnOXeoGmiPTtBqHTi2x3JE8ngxY4W5TWUaX7hGHf76DGPfE2u1Lnp6Eo+JIGcALVbHXnO/n KfajWwzEFD6IBnH/LUPxJYjrmDxcM157VdS+GgoQPPxxeSO3CZZwos41EAj1ryfc94CCdfB IitJo8vkquYvMzsmjUexA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:M9MWp+fbm7M=:Tw4JVcHyVrN1/RaaG1tBWc 04xHzm7jO7jQUx1kJcu1WJklrgnErq+drhkhhHupHASoChUuAvCXa/A3oB9mD74Dt2ASvlhmJ Wr6UBDNC1b3/EzaLZXQRnt6iBDQE/llM9WzgdQQ0WbedIwG3hfTAmsHtWzkKLR+ZykKI8YEwx 3ZMSZjHGpWGjkARcwvPT7ld26mbztSj/ydsstPw8pg6p3PtRCPJOP7wrxvNyPFV8boIy4sLep E9s1kAbyC0g1o1IT0/NyNTjBhDMcc+r3rzYC29rPyZGX49oAblfRyV4CGt5VG1u4s0mxcCC14 RUgxObQTgT+56/0pspVf5/Yueeh3dLTYF6XG1g2HcARmd1eEtBO3X+dj0n6faF8sqMTU8aKSr jkiU7hQ66v00gRt2PccXqVy+hHR6YySvSl6higCcp0GcaO1jZORBA1e6aMIdW0SHAOq2h7ZZ9 E1r2z4Qoi/xBlLFfLdtppxdgZm8JQnGWYbIIQB9KwA3pG3BFwQ5W6rRlZFcyZ0z0IgH6GWdfq J7whcOEJbNP/lc+tiFbDldkSw7GkHwCkv9jokIAn22w7sYhOxCnmZxXl++7zDkkOhEsOvhYAo tLAinqqjrnmoKhja0ygeRrT2Dm5EqL/AK1fdA7X1xMt/4Dp3N5CLGHzUSEJz7Z8LHjO8mXf8X KgaABbj0SFW4XQgJw2fQPfAk5h6jG1T2ySp3d03GIUXmTIugLDF373YLhag9T2az7FwM=
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/odU09YMK6PaFL3J6SZO6Ztm1mQI>
Subject: [icnrg] low-latency and scalable video distribution
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/icnrg/>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Mar 2022 10:19:58 -0000

Hello,

in case you missed it, the MOQ (Media over QUIC, https://datatracker.ietf.org/meeting/113/materials/agenda-113-moq-06) BOF at IETF-113 is discussing low-latency video distribution use cases.

The idea is to reduce latency for live streaming, i.e., achieving interactive conferencing latency without losing scalability.

The current thinking is using either RUSH (https://datatracker.ietf.org/doc/html/draft-kpugin-rush-00) or SRT over QUIC (meh ;-).

I believe that eventual solutions will have to do with stream prioritization, "relaxed" congestion control and incorporating the concept of relays.

Other topics/ideas that came up:

* application layer multicast
* local retransmissions
* content naming

Maybe something to look into from an ICN perspective...

Dirk