community about dtls HOT 4 CLOSED

@thomas-fossati let us know if you're interested in up-streaming your work. We're always looking to accommodate related efforts.

from dtls.

Hi Michiel,

Sure, it'd be great, two things though:

• There is a dependency on the upstream spec which we expect (finger crossed) to finalise in the next IETF cycle (between March and July);
• This specific feature impacts Pions' network layer, and since I do not master its internals, I'd need some pre-review help to check that I haven't done horrible things. If you have time, maybe you could precheck my fork for stupid mistakes?

from dtls.

Hey @thomas-fossati, that is awesome!

• Out of curiosity why did you choose to start hacking on this using pions/dtls?
• I would be more then happy to check out everything, if you do a rebase + wip pr I am happy to read through everything?
• Is there anything we can do to make this package better? Since you have read the code and poked around I am sure you saw some of my mistakes, anything I can do to make them better :)

Thanks!

from dtls.

Hi Sean,

Hey @thomas-fossati, that is awesome!

• Out of curiosity why did you choose to start hacking on this using pions/dtls?

Mainly because it looked like a well architected piece of software which I could understand and modify without major heartburns :-)

• I would be more then happy to check out everything, if you do a rebase + wip pr I am happy to read through everything?

Sounds good! I'm going to have some time to do that at end of this week.

• Is there anything we can do to make this package better? Since you have read the code and poked around I am sure you saw some of my mistakes, anything I can do to make them better :)

No particular comments for now, apart from "good work!". I've only stumbled upon one thing which looks like a bug.

from dtls.