Re: [icnrg] low-latency and scalable video distribution

Luca Muscariello <muscariello@ieee.org> Wed, 23 March 2022 17:18 UTC

Return-Path: <muscariello@ieee.org>
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 D5AEC3A0064 for <icnrg@ietfa.amsl.com>; Wed, 23 Mar 2022 10:18:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ieee.org
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 IhUR_-YyHq2Y for <icnrg@ietfa.amsl.com>; Wed, 23 Mar 2022 10:18:16 -0700 (PDT)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (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 CFB0E3A0063 for <icnrg@irtf.org>; Wed, 23 Mar 2022 10:18:15 -0700 (PDT)
Received: by mail-lj1-x233.google.com with SMTP id q14so2774493ljc.12 for <icnrg@irtf.org>; Wed, 23 Mar 2022 10:18:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3bTUFBkbLDKeV2I3Rd7BdRz8Ex7IvszRB6kSs81gcS0=; b=XDkB7ma1oy88Har7UJdnvB61n6cgPd1Ga+zRaomfgWZAwhtE6sPfiRWRkt5RDSY8rZ KbuFj/sNhRCrU6Ykacdet8UtXrSwYFV3AKgCICuzn+bzzJIiU8yEWh+mIS5F+ZRcPrYt ORGUOky/6ASkpl7J8UO5eZLPFct9r+Y52NN84=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3bTUFBkbLDKeV2I3Rd7BdRz8Ex7IvszRB6kSs81gcS0=; b=FJQStMPV/R69vaCcLFytXQuZ1EhNYR3xtq4SGgiOcubAvb/+oKbjWLfj8msB8vAs0t jYrao0iL8k/MwpcHv01zxMzGVr/yU2KG3vuk7kpun7aoeP/egrHzxDN4dRA+pl2Flyxq 7mHP8FCj1QZn9K0yuwMhRgjQbErBGT5IfpDl23tjO/9ZoxbBh4bkVYWvDGRj8B4yvnsP vUvYAymunLrzHHil4cWDiAEbisn1VbVzsA1N4w6yL8gWVjd/mJYNu6dppRBDK6pmcPSL RB+adGaHTLlejZiMVyEcsicqmnH/xeaBoGuEG6OPWltgOD+TdcBnkIFM9paQsZcH3v2Q TiLQ==
X-Gm-Message-State: AOAM530S6QmnlpdbaQqlXOPZJ2M0pZsnkr/pfYzS5K0/GzP3PsklKN3d vbTRb954zTnsKfaGCSeZINMi3DzbYWDQEgJPk6RuaIj0/hjGRQ==
X-Google-Smtp-Source: ABdhPJwa2br3/V8WWjJWEewmoxFW6L5Z15IOQCw5xEhTm1pZhVpQ5xh7+I7yACMpuHZ9619N5722PhHKGt68z1Eg6BQ=
X-Received: by 2002:a2e:a78f:0:b0:249:a0c4:7584 with SMTP id c15-20020a2ea78f000000b00249a0c47584mr858780ljf.494.1648055892961; Wed, 23 Mar 2022 10:18:12 -0700 (PDT)
MIME-Version: 1.0
References: <0E9B8F59-42EE-4BA0-B04D-E9A0A042CA06@dkutscher.net>
In-Reply-To: <0E9B8F59-42EE-4BA0-B04D-E9A0A042CA06@dkutscher.net>
From: Luca Muscariello <muscariello@ieee.org>
Date: Wed, 23 Mar 2022 18:18:02 +0100
Message-ID: <CAH8sseSTKb-NUDtuSbm8Yax_jJYbov8dXxTmjFBf=KQMuhYwhg@mail.gmail.com>
To: Dirk Kutscher <ietf@dkutscher.net>
Cc: ICNRG <icnrg@irtf.org>
Content-Type: multipart/alternative; boundary="00000000000012838405dae5ea88"
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/nmur8-C-8eEyyCAdIB9Lhbo56fo>
Subject: Re: [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 17:18:21 -0000

Hi Dirk

I was aware of these preliminary discussions but I'm still trying to
understand
the benefits of media over QUIC, beyond going through UDP port 443.
Even though network traversal for RTP has never been a major problem.
I would wait to see some data about the advantages as soon as they are
available.

I'm interested in the list of topics you have just made, which looks
very close to our own agenda: Scalability and infra offload via multicast
and
load balancing, reliability, content naming and security for real-time
applications.
In our team at Cisco this is an important use case.

One past reference here:

M. Papalini *et al*., "On the Scalability of WebRTC with
Information-Centric Networking," *2020 IEEE International Symposium on
Local and Metropolitan Area Networks (LANMAN*, 2020, pp. 1-6, doi:
10.1109/LANMAN49260.2020.9153228.

ICN looks like a perfect match for these applications.
@Marie-José we have now included coding by default in our hicn code base
and not only for real-time transport. It's definitely useful.

There is a big hicn code refactoring coming this week, or early next week
in case all tests take longer to pass, in the linux foundation repository,
with major emphasis on these use cases.
At least for those who are interested in the code base.

Luca


On Wed, Mar 23, 2022 at 11:20 AM Dirk Kutscher <ietf@dkutscher.net> wrote:

> 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
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg
>