Re: [quicwg/base-drafts] Priority in QUIC Transport (#104)

[Martin Thomson <[e-mail]>]

This is worth discussing.  An important lesson from HTTP/2 was that multiplexing is lame without prioritization.

@MikeBishop, I assume that you are thinking one of two things:

1. move the entire prioritization feature to the QUIC layer
2. a more complex arrangement in which stream prioritization is determined by the application layer protocol, but the transport queries the application layer to learn what packets to allocate resources to

I agree that the status quo isn't ideal.  Mostly that's theoretical, because an implementation can add as much cross-talk between layers as it needs to get the job done.  It could mean that retransmissions of packets are made in ignorance of priority.  Speaking of which, we probably need some sort of guidance about how to prioritize those.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/104#issuecomment-270295768