You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we receive a duplicate NEW_CONNECTION_ID for the the connection ID that's currently in use, we immediately send a RETIRE_CONNECTION_ID frame for that connection ID, without actually retiring it.
That means that this connection ID is retired in a packet that uses the same connection ID. This is a protocol violation. More importantly, since we never actually retire the connection ID, packets will end up getting dropped as soon as the peer drops the association between that connection ID and the session (which happens after 5 seconds in quic-go).
The text was updated successfully, but these errors were encountered:
When we receive a duplicate NEW_CONNECTION_ID for the the connection ID that's currently in use, we immediately send a RETIRE_CONNECTION_ID frame for that connection ID, without actually retiring it.
That means that this connection ID is retired in a packet that uses the same connection ID. This is a protocol violation. More importantly, since we never actually retire the connection ID, packets will end up getting dropped as soon as the peer drops the association between that connection ID and the session (which happens after 5 seconds in quic-go).
The text was updated successfully, but these errors were encountered: