Port DTLS code to Native Go (instead of OpenSSL)

[Sean-Der]

This is a huge task, but if someone is up for it I won't stop them :)

When I get around to this I will assign to myself and start the long task. Also more then happy to split the task/get guidance if you are familiar with DTLS/have opinions on how the API looks but don't have time to do the coding.

[nicolai86]

The relevant RFC for this is RFC 6347 , correct?

[backkem]

Yes, there's also an overview of RFCs on the wiki.

[ghost]

There is an existing DTLC golang implementation..

Background:
The go team have an issue for a pure golang dtls implementation:
golang/go#13525
But they are still holding out from putting a go team supported package into the go crypto library.

In that issue, the most promising DTLS implementation highlighted is this:
https://github.com/bocajim/dtls

@bocajim @backkem

Sounds like there is some strong synergy here to get this done ?

@bocajim: Your code says it implements RFC-4347, and the webrtc team have said they need RFC-6347 ( see the wiki page at https://github.com/pions/webrtc/wiki/Relative-Drafts-And-Usages#dtls ).

https://tools.ietf.org/html/rfc4347 say that it is obsoleted by RFC-6347, so this makes sense.
RFC 4347: DTLS Version 1.0
RFC 6347: DTLS Version 1.2

[Sean-Der]

I moved this to our Project Ideas

[ghost]

@Sean-Der
there are many good c DTLS, and so maybe a conversion like what the golang team often do. For example when they had to charge the compiler itself from c to go.

https://github.com/elliotchance/c2go

[trivigy]

@gedw99 Did you end up trying the c2go route?

[ghost]

No I have no time unfortunately.

I think it's worth a shot and I know Elliot behind the project is very supportive so it's worth trying