Daenney

I was looking at this, and the main issue seems to be that description exists on `Parser`, instead of on `command`. Moving the field is fairly easy, but then we...

@Sean-Der Do you know why this is? Looking at our code, the only thing we use from Conn that PacketConn doesn't have is the RemoteAddr, but since using ReadFrom on...

I'm not a 100% sure I'm following. Are you saying that after a reboot your client is not able to reconnect to a server?

I don't have any issue with it, though it's worth noting the RFC said "should", not "must", when it comes to supporting this feature. This would indicate to me clients...

pion/dtls is used by quite a few projects outside of the WebRTC ecosystem, for which this wouldn't be appropriate at all. I don't think we should be special casing certain...

The behaviour is usually configurable on the server side. Apache/nginx etc used to have a `prefer_server_ciphers` at which point it would iterate through the server ciphers and pick the most...

Sending a ServerHello with the RSA suite but then following up with a ServerCertificate with an ECDSA cert sounds like a bug on our side. That should never happen, regardless...

I'm probably misunderstanding the problem, but can't we use a buffered channel to get around this? ```go var conns := make(chan net.Conn, 100) hub := util.NewHub() go func(l net.Listener) {...

Oh mm, the Accept is on dtls.Listener, so that triggers the whole handshake machinery. We should be able to Accept() on the underlying listener first and then spin the rest...

If we were to take option 1, realistically we'd want that option on/by default since the current behaviour is undesirable. But we can't flip that on by default since it...