Michał Śledź

Sounds good :+1: If we decide to introduce them we also should consider some constraints on maximal number of such events to store.

This could be an event property i.e. we set if event should be overriden or not because in DTLS-SRTP scenario there can be multiple events of the same type each...

Hi @iihres, does it crash application? I think that we see the same warnings and you shouldn't be worried about them

``` [warn] [{:srtp_decryptor, #Reference}] Couldn't unprotect rtp packet: Reason: :auth_fail. Ignoring packet. ``` This might be interesting. Does it repeat or it occurs only at the beginning of the communication?

Hi @iihres, we are thinking about this but at this moment there is no sense to use client library without server library and this is very first version of our...

Good point. We will take this into consideration. Let's leave this issue open until we publish a client library in npm or decide not to do it.

Hi @michalslaski, I am sorry for the quality of my first message. I have no idea why it was so messy (fixed it a little bit). I wanted to try...

Actually it's not so important. I forgot about qlog and qvis. The real question I wanted to ask is why `STREAM_DATA_BLOCKED` frame is sent so early. Here are my qlog...

> To answer your original question, Wireshark should definitely be able to decode QUIC v1 packets, though you might need a recent version (according to https://github.com/quicwg/base-drafts/wiki/Tools#wireshark you need at least...

[client_trace.log](https://github.com/cloudflare/quiche/files/6758239/client_trace.log) [server_trace.log](https://github.com/cloudflare/quiche/files/6758245/server_trace.log) [server.qlog.txt](https://github.com/cloudflare/quiche/files/6758247/server.qlog.txt) [client.qlog.txt](https://github.com/cloudflare/quiche/files/6758248/client.qlog.txt)