I’ve recently started implementing NoiseSocket in Python noiseprotocol. First thought: would be nice to have at least default proposed contents for negotiation data. Otherwise we’ll likely end up with implementations freely following structure in Alexey’s go-noisesocket (or e.g. mine if I decide to come up with my own). Obviously, usage of this default structure won’t be necessary, nor explicitly suggested. <div class="gmail_quote"><div dir="ltr">W dniu czw., 9.11.2017 o 07:21 Trevor Perrin <<a href="mailto:trevp@trevp.net">trevp@trevp.net</a>> napisał(a): </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Nov 3, 2017 at 8:37 PM, David Wong <<a href="mailto:davidwong.crypto@gmail.com" target="_blank">davidwong.crypto@gmail.com</a>> wrote: [Trevor]: >> It's not an either/or, since NoiseSocket is built on top of the Noise core. >> >> As for encouraging Noise libraries to also implement NoiseSocket or >> any other Noise-based protocol: I'd encourage people to experiment >> with NoiseSocket. But NoiseSocket is young, and probably needs a lot >> more work and implementation/deployment experience before we have any >> confidence that it's the right direction. >> >> But to figure that out, we need to try it! >> > > Totally, > The experiment will also be more productive if we also have some > guidance from you as to what we should implement and test :) I'm not sure NoiseSocket has been implemented outside of Alexey / Virgil Security, so any feedback on that document is useful: Is it easy to understand and implement? Does it work for different use cases? What else do we need to add or build on top of it, etc. Trevor _______________________________________________ Noise mailing list <a href="mailto:Noise@moderncrypto.org" target="_blank">Noise@moderncrypto.org</a> <a href="https://moderncrypto.org/mailman/listinfo/noise" rel="noreferrer" target="_blank">https://moderncrypto.org/mailman/listinfo/noise</a> </blockquote></div>