On Mon, 26 Oct 2020, 12:49 Flinck, Hannu (Nokia - FI/Espoo), < [email protected]> wrote:
> Hello Lucas > > > > No, there are multiple QUIC connections (multipath!). Please see slide #5 > in > > > https://github.com/quicwg/wg-materials/blob/master/interim-20-10/Multipath%20in%203GPP%20ATSSS.pdf > > > > Bulk data and low-latency are kept separate. Each QoS flow has its own > connection. > > > I'm not talking about the ATSSS tunnel part. I'm saying, when a QUIC client and server want to multiplex different kinds of traffic in the same connection, the transport let them do that using streams and datagrams with application-specific scheduling. I don't see an answer for how ATSSS can distinguish the different traffic in end-to-end QUIC. So I don't see how it can select the different paths that it knows about but the endpoints don't. If the answer is something like "keep your different traffic on different end-to-end connections." then that is a very sorry state of affairs and undoes many benefits. So I'm hoping there is something I'm missing. Cheers Lucas >
