-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Joscha,
Congratulations on releasing this source code. I believe that, even more than for other Internet protocols, code diversity for RELOAD is an important foundation for resilient deployments. May I suggest that you repost this in the RELOAD implementers[1] mailing-list? I have some questions on your implementation that are probably off-topic here. Thanks. [1] http://implementers.org/mailman/listinfo/reload On 12/20/2012 07:44 AM, Joscha Schneider wrote: > Hello all, > > Just before Christmas we are pleased to announce a prototype RELOAD stack > called RELOAD.NET available as open source. The stack originated from > T-Systems in Darmstadt, Germany and has been extended by University of > Applied Sciences in Hamburg and University of Applied Sciences in > Mannheim. > > First and foremost, the stack is slightly behind the actual draft, some > important features are missing and the further development depends on > potential developers willing to put effort into the stack. > > The implementation is written in C# based on the .NET framework version > 4.0. The source code is compiled to a library that allows using the stack > as a C# assembly. > > RELOAD.NET is hosted on GitHub at: > > https://github.com/RELOAD-NET/RELOAD.NET > > The RELOAD.NET library implements all the layers as defined by the RELOAD > architecture. This includes the Usage Layer allowing the implementation of > further Usages and the Message Transport, which relies on the Chord > algorithm that is implemented within the Topology Plugin. The Storage Layer > has the ability to store all three mandatory data types (value, array, and > dictionary). Further, the Forward and Link Management Layer uses the > commercial Eldos Secure Black Box (SBB) library to realize the transport > using TLS. Also, the SBB is used for the certificate handling. > > Although RELOAD.NET represents a rather advanced implementation, some > requirements specified by the draft are missing. In particular, the > implementation of the ICE connection establishment is missing. Also, the > implemented message fragmentation isn’t compliant to the draft. > > So far the documentation is lacking. For the basics we have set up a Wiki > on GitHub: > > 1) Getting Started gives an overview how to set up the RELOAD.NET > project using Visual Studio. > > https://github.com/RELOAD-NET/RELOAD.NET/wiki/Getting-Started > > 2) Running the Stack explains briefly how the stack is configured and > a RELOAD peer started. > > https://github.com/RELOAD-NET/RELOAD.NET/wiki/Running-the-Stack > > 3) Open Topics will be used to list potential topics for further > development. So far most important is the elimination of the proprietary > SBB component. > > https://github.com/RELOAD-NET/RELOAD.NET/wiki/Open-Topics > > The stack’s future depends highly on voluntary developers. We are aware of > some constraints that aren’t ideal for an open source project but we hope > that enthusiastic developers might contribute to expedite the > implementation. > > To set up a configuration and enrollment server we refer to the service of > Marc Petit Huguenin: > > http://blog.marc.petit-huguenin.org/2012/08/a-configuration-and-enrollment-service.html > > > > For further information including GitHub push permissions please don’t > hesitate to contact me. > > Kind regards and Happy Holidays, > > Joscha Schneider > > University of Applied Sciences Mannheim > > Institute for Software Engineering and Computer Networks > > [email protected] <mailto:[email protected]> > > - -- Marc Petit-Huguenin Email: [email protected] Blog: http://blog.marc.petit-huguenin.org Profile: http://www.linkedin.com/in/petithug -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQ2cTkAAoJECnERZXWan7EXxsQAOGqxgSQD1E9MzhPvpmKIdSw Ob6+gowtIokdKNqzgaixJLeWaMvtMwa31YAfxxz7gIC3mc3ZnSrmVEax5moGWiys EHCgwNN3KUgM1o+esxYeibNMfCz4UuyxHlq1oCXG4Gj9gqtq6eeugKptHqUYubLH n9ypOZshl+5mz1ZuAWDMo21ZGqd9x048dI6FRutPJCRpmEgMl6wu4hMVxd5SY4xG AiFRn1Z6aS36TYn5VOmOuAAe8m5PhNLoCqf0B3MOzIQpc/xucUq63/iE/E+5keV5 jY1kpssov8bvzjwTW2IJQpbZu2DcJKUULo5mEDlzzRrLOm+gE8gL8Lc1GSdc9WqW Prj5mo/k+GjrCkLoXQRKeBKiJoch2iMTvkHzAg2QgkQv59e/Zil/q+jAmiKT4SoZ +sX0NI7ViWGggZPj4jxyNrE+lc5UG26yzJ/I+fEjUwNGMw6a7jfl/o6IOwvbrpk7 V5/hQKOoBAuhGOZgitiiGDw/QlcovMeB7PHssXPh1AunTzXrIaWjjmxxkugWyDVx 9TSAQOoyNNxAtM0oUzjq8gG4EfOTFvKepJtDVuCAmq77zNYlPZWV63jnrsJuGuRG KY0UopdyARZbOKiVfo27mCB582W6lRo7jkQOUZhVgstmh2C/00m2QnOkN1hfWUiO PQrnTA0nIwKAMgZuo8xF =J+8j -----END PGP SIGNATURE----- _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
