[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cf-dev] Replacing the element-connector with Netty -- thoughts?
|
Hi Matthias,
I am not really sure if I understand your proposal correctly.
Are you talking about simply replacing the interfaces defined by element-connector with interfaces defined by Netty or are you talking about re-implementing Scandium based on Netty? Or maybe both, first the former, then the latter?
The former seems to have the benefit of being able to (potentially) employ existing protocol implementations (available from the Netty community). However, since I have no experience with Netty, I am not sure if the Netty abstractions (interfaces) could actually serve as a replacement for element-connector.
Regarding the latter, I would actually welcome such a step. I think you have done a great job in creating a working version of DTLS from scratch. But in order to move this forward to IoT scale I think we would need to do a lot of re-factoring in the Scandium code anyways. Thus, this would be a great opportunity to take advantage of the proven concepts available in Netty for re-implementing DTLS. In this context we should also think about "outsourcing" the crypto code to a JCE provider like Bouncy Castle in order to take advantage of peer-reviews from people who know their (crypto) latin ...
Regards,
Kai
> -----Ursprüngliche Nachricht-----
> Von: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx] Im
> Auftrag von Kovatsch Matthias
> Gesendet: Dienstag, 17. März 2015 19:45
> An: Californium (Cf) developer discussions
> Betreff: [cf-dev] Replacing the element-connector with Netty --
> thoughts?
>
> Hi all
>
> I have been thinking about getting rid of the element-connector since I
> created it. It was introduced to decouple Scandium from Californium, so
> that it can be used as stand-alone DTLS implementation. Netty [1] is a
> powerful framework that provides something similar (actually much
> more). While getting rid of the custom element-connector, it might also
> lead to a performance gain.
>
> Since Simon Lemay is now working on the TCP/TLS binding, it appears to
> be a good time to start with the replacement. Simon checked that Netty
> is also supported by Android and runs on the Raspberry Pi.
>
> Any comments? Does anyone have experience with Netty, maybe situations
> where it actually did not fit?
>
> For the long-term, it might also help for DTLS. Netty does not have
> DTLS yet, but I would say they need it. Scandium is by no means a high-
> performance implementation and still requires lots of work, in
> particular for testing and security analysis. But maybe we can get more
> contributors or an alternative that is better for both communities!
>
> Ciao
> Matthias
>
> [1] http://netty.io/
> _______________________________________________
> cf-dev mailing list
> cf-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit https://dev.eclipse.org/mailman/listinfo/cf-dev
