Dragana Damjanovic

In the case of WebTransport we have WebTransportEvent::Negotiated that is posted when support for WebTransport is known, i.e. it is supported by the server or not. This is basically posted...

PushDataReadable should probably also have a stream_id field as well

1

this will make possible to have just one function to read from a push or response stream

We need stats for traffic in both direction. count number of send/receive DATA_BLOCKED frames with a unique value. Add these stats to: https://github.com/mozilla/neqo/blob/master/neqo-transport/src/stats.rs

HTTP Priorities

1

https://httpwg.org/http-extensions/draft-ietf-httpbis-priority.html

The copy that happens here is a little unfortunate. It might be a good idea to mark this for future investigation. I don't think that a copy is going to...

HTTP priority should have an effect on neqo-transport priories

1

neqo-tranpsort implements priorities defined [here](https://github.com/mozilla/neqo/blob/37bb62fa7b43ac624406090ba4f94f4cc082790b/neqo-transport/src/send_stream.rs#L36). They are: Critical, Important, High, Normal, Low. "Critical" should not be used for streams, therefore 7 HTTP priorities should be matched on these 4 priorities.

Re-prioritizing requests that have started a transmission

3

If neqo has started transmitting data on a stream, should it change its priority? It is better to finish sending a request so that the server can actually respond to...

Currently Datagrams are delivered as events, I think we should have a separate API for datagrams so that they can be handled independent of other connection events.

I know that this is old code, but shouldn't we be checking that - for a request, we DON'T get :status? That means we need a set of bits that...