Here's my abstract for the crypto library proposal. Any feedback would be greatly appreciated!

"This proposal describes the porting of the cryptography library Botan and its integration with ASIO

Botan is released under the BSD license and the author has already agreed to porting it.

Does this mean you will be converting the source-code of Botan to Boost standards or you are going to wrap it? 1. If it is conversions two issues may rise: a) License Botan is licensed under BSD license with is different from Boost and all the code you will write for boost would not have correct license. b) Conversion to Boost means fork... How do you expect to synchronize changes in two libraries and most important security updates. This means lots of work in the live cycle of Boost.Botan 2. If you are wrapping it. - Why just not write module to ASIO that would use Botan instead of SSL? - What is the benefit of wrapping it would bring over using original, license that is actively maintained? Additional points: - Botan uses GNU gmp library licensed under LGPL... Does it fit to Boost licensing guidelines? - I think that you should be really specific what would be the advantage of using Boost.Botan library over original Botan one or OpenSSL that Boost.Asio uses. Artyom