Stuart Stock

> the current implementations assumes the key must be decrypted into system memory, and the delegation signed in software Very good point. The current design is entirely software oriented for...

@zicklag Agreed. If you can provide the Drone script I'll integrate it with the CI pipeline. Thanks for this, and for the PR!

Related to #1. The artifacts produced would likely be: * `protocol` - the base Roughtime protocol implementation * `client` - the client API * `server` - stand-alone server implementation

Hello @cjpatton , thanks so much for kicking off the interop testing! I'll take a look at your suggestions and work on getting the two implementations working together.

Hi @cjpatton, > Relatedly, like you we wanted to run both the Google and IETF versions from the same port. How did you accomplish this? We use the "ROUGHTIM" prefix...

@cjpatton I made some changes to this implementation to support private prefixed versions, specifically to send VER value`0x80000008` for Draft8 to be compatible with the latest Cloudflare implementation. This client...

@cjpatton closing this issue now that draft8 is interop'ing. Tracking your draft10 implementation and this one's in #40.