Sean DuBois

@daenney yep exactly! @jkralik agree! ---- [Server]( https://github.com/golang/go/blob/master/src/crypto/tls/tls.go#L35-L41) in `crypto/tls` doesn't actually do anything so we need to match this API. Instead the first call to `Read` or `Write` should...

It looks like we will need to do a `v3` and add [Handshake](https://golang.org/pkg/crypto/tls/#Conn.Handshake) I can't believe I missed this before :( this is a pretty big breaking change, but I...

> I'm not sure, when exactly the spawned goroutine is required. @boaks Each `Accept` call would be in one. You would do a pre-allocated pool, so I don't think the...

Hi @niondir Instead of doing your `Handshake` or first `Read`/`Write` in a goroutine create your `dtls/Conn` in one. Even when we change the behavior to match `crypto/TLS` you still have...

@glerchundi I would love to do this! I wasn't aware of the Connection ID work. This sounds really amazing, this could allow people to load balance WebRTC traffic finally.

Hey @hjames9 We can expose statistics if that is helpful! I think that would be a great contribution, I am not sure what that would look exactly like yet though....

Hey @tigersean We close when we get a [Close Alert](https://github.com/pion/dtls/blob/master/conn.go#L720) We also send a [Close Alert](https://github.com/pion/dtls/blob/master/conn.go#L903-L905) when the user closes the connection.

Hey @bocajim! Great work on your DTLS implementation. You inspired me a lot, convinced me that it was possible to implement DTLS in Go :) Even though if this cost...

I just need a `OnClose` or some sort of status callback. DTLS already closes for me (I have a reliable connection over WebRTC) and a loss of connection is handled...

@rumpelsepp what do you think of doing something like `RequestWithContext` ? https://golang.org/pkg/net/http/#NewRequestWithContext