Re: QUIC use with multicast

[Lucas Pardue <[e-mail]>]

Hi Gyan,

Speaking as an individual, and author on the above mentioned I-D, I think
you've touched on quite a few interrelated topics in quite a succinct
question. Teasing them apart a little bit, the things that stand out to me
are listed below. Many of turn out not to be QUIC specific, or even
multicast specific, and are probably better addressed in various other IETF
WGs or areas; some under active discussion right now.

* Interdomain multicast on unmanaged networks (including ingress to or
egress from cloud providers). Covering both vanilla MBONE-like deployments,
or some kind of tunnelling between publisher and subscriber
* Multicast in managed networks.
* Multicast in WiFi networks.
* "Congestion control" or how to avoid detrimental over subscription.
Covering both accidental and malign causes.
* Management and Operability of multicast and video-oriented traffic more
generally.
* Loss detection and recovery. Including tunable FEC.
* Discoverability, handover and fallback.
* Confidentiality, Authentication and Integrity.
* Unidirectional transports (of at least one path in a "connection").
* Mapping of application layers to QUIC. For your example, RTP over QUIC
might be achievable via encapsulation in DATAGRAM[] frames or a
more-specific TRP application mapping document e.g.
draft-rtpfolks-quic-rtp-over-quic-01.

Cheers
Lucas