Daenney

UDP doesn't really have connections, so we'd basically have to have a mechanism client side that's configured with a value for a timeout, after which we consider the server to...

I would imagine that if the server restarts you'd be getting errors though, as the TLS session is no longer valid. Though I suppose you'll only ever see that if...

Turns out I'm wrong on being able to detect a restart. DTLS implementations silently ignore invalid records, so there's no way to detect that. > Unlike TLS, DTLS is resilient...

The problem I see with this is that we can never reliably know if a connection is closed, since there is no connection. We're just screaming into the void hoping...

I hadn't seen that before! It turns out we made a decision before in #15 to not implement this though. It appears to have some security implications, being at the...

Heartbleed was an implementation mistake on the heartbeat mechanism. As pointed out in #15, at least LibreSSL pulled support for the mechanism entirely over it. From what I can gather...

Take a look at https://github.com/pion/dtls/blob/master/examples/listen/psk/main.go. I think that's what you want? Configurability wise, whatever nobs exist on [dtls.Config](https://github.com/pion/dtls/blob/2e643d98a435e17c0cd7b87bcd421fe11a0a0632/config.go#L20) you can use.

Certificates aren't used if you configure PSK.

I think that's a typo in the docs. I believe it should be "Servers MUST set this if PSK is nil". Just don't set it in your `dtls.Config`. Also, if...

Interesting. So that seems to happen due to https://github.com/pion/dtls/blob/2e643d98a435e17c0cd7b87bcd421fe11a0a0632/flight3handler.go#L38 most likely. I believe that should be conditional on a PSK client identity hint being set, and if it's not we...