Original text:
5. Our proposal is that "Media Over QUIC" discussions focus first on the <del> use cases for Live Media Contribution (lmcont), Syndication (lmsynd), and Streaming (lmstream).  Our reasoning is provided in usecaseanalysis. </del>  5.1. Each of the above use cases in overallusecases fit into one of three classifications of solutions. <del> The first group, covering gaming (gaming), screen sharing (remdesk), and general video conferencing (vidconf), are largely covered by WebRTC and related protocols today.  Whilst there may be benefit in these use cases having a QUIC based protocol it may be more appropriate given the size of existing deployments to extend the WebRTC protocol and specifications.  Such work could start in a QUIC specific forum, but would likely need to take place in rtcweb and the W3C. The second group of classifications, covering Live Media Contribution (lmcont), Syndication (lmsynd), and Streaming (lmstream) are likely the use cases likely to benefit most from this work.  Existing protocols used such as HLS RFC8216 and DASH DASH are reaching limits towards how low they can reduce latency in live streaming and for scenarios where low-bitrate audio streams are used add a significant amount of overheads compared to the media bitstream. On-Demand media streaming (odstream) is unlikely to benefit from work in this space.  Without notable latency requirements, protocols such as HLS and DASH largely meet the needs of this use case. </del>  6.

Reviewer comments:
It's likely that only NAME and I will care about this, but I think it matters :grin:

Revised text:
5. Our proposal is that "Media Over QUIC" discussions focus first on the  <ins> use cases described in lm-media, which are Live Media Ingest (lmingest), Syndication (lmsynd), and Streaming (lmstream).  Our reasoning is provided in usecaseanalysis. </ins> 5.1. Each of the above use cases in overallusecases fit into one of three classifications of solutions.  <ins> The first group, in interact, covering gaming (gaming), screen sharing (remdesk), and general video conferencing (vidconf), are largely covered by WebRTC and related protocols today.  Whilst there may be benefit in these use cases having a QUIC based protocol it may be more appropriate given the size of existing deployments to extend the WebRTC protocol and specifications.  Such work could start in a QUIC specific forum, but would likely need to take place in rtcweb and the W3C. The second group of classifications, in lm-media, covering Live Media Ingest (lmingest), Live Media Syndication (lmsynd), and Live Media Streaming (lmstream) are likely the use cases likely to benefit most from this work.  Existing protocols used such as HLS RFC8216 and DASH DASH are reaching limits towards how low they can reduce latency in live streaming and for scenarios where low-bitrate audio streams are used add a significant amount of overheads compared to the media bitstream. The third group, od-media, covering On-Demand Media Ingest (od- ingest) and On-Demand Media streaming (od-stream) is unlikely to benefit from work in this space.  Without notable latency requirements, protocols such as HLS and DASH largely meet the needs of this use case. </ins> 6.