Re: QUIC use with multicast

David Waring <david.waring@rd.bbc.co.uk> Fri, 17 January 2020 10:23 UTC

Return-Path: <david.waring@rd.bbc.co.uk>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4543E120071 for <quic@ietfa.amsl.com>; Fri, 17 Jan 2020 02:23:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 4F55S7bImY0b for <quic@ietfa.amsl.com>; Fri, 17 Jan 2020 02:23:35 -0800 (PST)
Received: from tlsmtp.bbc.co.uk (tlsmtp0.cwwtf.bbc.co.uk [132.185.160.172]) (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 5331D120047 for <quic@ietf.org>; Fri, 17 Jan 2020 02:23:35 -0800 (PST)
Received: from gateh.kw.bbc.co.uk ([10.118.193.77]) by tlsmtp.bbc.co.uk (8.15.2/8.15.2) with ESMTPS id 00HANWP4003665 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <quic@ietf.org>; Fri, 17 Jan 2020 10:23:33 GMT
Received: from mailhub0.rd.bbc.co.uk ([172.29.120.128]) by gateh.kw.bbc.co.uk (8.14.5+Sun/8.13.6) with ESMTP id 00HANWJI029757 for <quic@ietf.org>; Fri, 17 Jan 2020 10:23:32 GMT
Received: from goliath.rd.bbc.co.uk ([172.29.90.42]:32898) by mailhub0.rd.bbc.co.uk with esmtp (Exim 4.92) (envelope-from <david.waring@rd.bbc.co.uk>) id 1isOmq-0008B5-A0 for quic@ietf.org; Fri, 17 Jan 2020 10:23:32 +0000
Subject: Re: QUIC use with multicast
To: quic@ietf.org
References: <CABNhwV38byx28ayEjw5YBJdQ6Oc4BSxnC++rAHMTjHJcLTn2JA@mail.gmail.com>
From: David Waring <david.waring@rd.bbc.co.uk>
Message-ID: <50b1f5ae-bf18-1b0a-183a-e40b2bbe969c@rd.bbc.co.uk>
Date: Fri, 17 Jan 2020 10:23:32 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1
MIME-Version: 1.0
In-Reply-To: <CABNhwV38byx28ayEjw5YBJdQ6Oc4BSxnC++rAHMTjHJcLTn2JA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/seb0Mamoc1Fgh09c2uw57LsBxPg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2020 10:23:40 -0000

Hi Gyan,

You might want to look at
https://datatracker.ietf.org/doc/draft-pardue-quic-http-mcast/
which looks at using HTTP/3 in QUIC over IP multicast.

It not as simple as just using QUIC in multicast. As you point out, 
there are unidirectional streams, but these are encapsulated within a 
bidirectional QUIC session. The bidirectional nature is required to make 
the protocol reliable. Unfortunately bidirectional doesn't work well 
with multicast.

The draft above makes the stream truly unidirectional by removing the 
ack system on the QUIC multicast session, which removes the reliability, 
but also means that the session no longer needs to send anything back 
from receiver to sender. A separate bidirectional unicast session is 
used to fill in any gaps in the data streams received.

Another solution, which we considered as too complex at this stage, is 
to use multipath, with the unicast session being setup but using a 
second unidirectional multicast path to deliver the majority of shared 
content (live video stream for example). This would however require a 
separate packet number space for the multicast stream in order to share 
that path between multiple connections, which complicates the ack system 
and isn't catered for in the current incarnation of QUIC. But this is 
something we may look into in the future.

Regards,
David

On 17/01/2020 02:05, Gyan Mishra wrote:
> 
> QUIC WG
> 
> Has anyone ever tried using QUIC with multicast RTP UDP streamed using 
> QUIC transport.
> 
> Multicast has always been problematic with use on the internet MBONE and 
> even on intranets due the unreliable UDP RTP transport for MPEG4 MPEG-TS 
> and even newer protocols MPED-DASH abs and HLS multicast has struggled 
> with using UDP transport.
> 
> Multicast has thus required stringent end to end QOS in profile 
> guaranteed scheduling bandwidth hop by hop PHB to ensue no drops to 
> avoid dropping of I frame resulting in client frozen window and buffering.
> 
> Since QUIC is a secure reliable transport and supports unidirectional 
> flows it would be a perfect fit for multicast.
> 
> This would be a game changer for multicast as over the internet which 
> you don’t have any QOS guarantee.
> 
> Kind regards
> 
> Gyan
> 
> 
> -- 
> 
> Gyan  Mishra
> 
> Network Engineering & Technology
> 
> Verizon
> 
> Silver Spring, MD 20904
> 
> Phone: 301 502-1347
> 
> Email: gyan.s.mishra@verizon.com <mailto:gyan.s.mishra@verizon.com>
> 
> 
> 
-- 
David Waring, Project Software Engineer, BBC Research & Development