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

Marie-Jose Montpetit <> Wed, 23 March 2022 10:44 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D1C0B3A15ED for <>; Wed, 23 Mar 2022 03:44:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Mu8IdRzXhUVG for <>; Wed, 23 Mar 2022 03:44:10 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 390F53A0DB0 for <>; Wed, 23 Mar 2022 03:44:10 -0700 (PDT)
Received: by with SMTP id u3so1285349ljd.0 for <>; Wed, 23 Mar 2022 03:44:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=W+ijuwaA0ix+JhEr0JtvLo2sNV/OXMu4BW803qlVlFg=; b=1ajkpGoLI3o9bjw8VZZ1a1DzSe2neA8Mqa4PaG2Vcff1WU98d5IHOG/kw/x9jzVVKF W3XbBH8/KbWe2LbKP/YY1A97LBY4L4KWgh7dCw5u3TcYKO6jlcc50URyFjTi2jg8e3a7 4kqCs1YrWcnjqfQPlWBg+CNmqY6yUbK+MgXBi6tHxsH9wN/Nh+3nKBycoS+bRunnjlLn KCEgwut1I0h/H6DdIJC6bvkdKayID+Vueu8Ks5JFhKV6v40/hV29+nMFQvOAPrkbe9CD 39aVkcVThkmKiXcA7KKEufNK4sJ1rkxNyWxNDeWlpyPFxp8fNkCnr1rpWJxKu2RbSVHd IQkw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=W+ijuwaA0ix+JhEr0JtvLo2sNV/OXMu4BW803qlVlFg=; b=vtA4VS9WJGrw+24zHYIM3/ZZL1tW7t1QM31O5fqYmiLOcFYtMMg7ngtTV4laZfqzdW X/2rSmbGTUVZqgCwSHSqLif83QPz/tyeu2n3h39V6noHiVaCUyspHn9eEFguDxveYiB0 dHCJunjkFRCjgs1qTdQf3g4pix0bNcqOzW/B9enePR99prHWsejEOHTiBeHNO7cPtxkP Up716XbHnPpGiO7+mwcOZLLeHINYsK+RoAOBhjA/ymjyCKXJzuvBKXAz54stYGjSX0Da cRq5X0HqTNR4UM32wDxG25TLpzUCzHslLyPPvWPB/Aa+qiFGRlokwWulk4KtwcnxxUBD nH3g==
X-Gm-Message-State: AOAM532HuG2knJAcMr3/2LlVJD4+S9nHAkLt+FrSEZK886PWyNAhAk5y aQM3FT+P9dATvYHi9VY2G+9MQ1P44QXnHhnhiP5rsvFDG6M=
X-Google-Smtp-Source: ABdhPJycX7sdlMS/nEXxsdPFZ0BvBAqQzx80XKdmfj3m7M0sw0/R4bqyN/rT9wjfA6vel10tXod8f1DFIrrN0GsWNCg=
X-Received: by 2002:a2e:b55b:0:b0:247:e52e:75f3 with SMTP id a27-20020a2eb55b000000b00247e52e75f3mr22454657ljn.260.1648032247749; Wed, 23 Mar 2022 03:44:07 -0700 (PDT)
Received: from 1058052472880 named unknown by with HTTPREST; Wed, 23 Mar 2022 06:44:07 -0400
From: Marie-Jose Montpetit <>
In-Reply-To: <>
References: <> <>
MIME-Version: 1.0
Date: Wed, 23 Mar 2022 06:44:07 -0400
Message-ID: <>
To: ICNRG <>, Dirk Kutscher <>
Cc: nwcrg <>
Content-Type: multipart/alternative; boundary="000000000000b4b56905dae0686d"
Archived-At: <>
Subject: Re: [icnrg] low-latency and scalable video distribution
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Information-Centric Networking research group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 23 Mar 2022 10:44:21 -0000

Many use cases seem to suggest reasons to bring back coding in QUIC.


Marie-José Montpetit, Ph.D.

From: Dirk Kutscher <> <>
Reply: Dirk Kutscher <> <>
Date: March 23, 2022 at 6:22:24 AM
To: ICNRG <> <>
Subject:  Re: [icnrg] low-latency and scalable video distribution

Here is a comprehensive presentation that includes most of the aspects I


On 23 Mar 2022, at 11:19, Dirk Kutscher wrote:


in case you missed it, the MOQ (Media over QUIC, 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 ( 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...


icnrg mailing list

icnrg mailing list