Planning to split TLS 1.3 into a standalone library

[colocohen]

💡 Planning to split TLS 1.3 into a standalone library

Hi everyone 👋

I’m planning to split the TLS 1.3 implementation out of quico into its own standalone library.
The idea is to make the TLS layer reusable outside of QUIC — for example, if someone wants to build DTLS, custom transports, or other TLS-based protocols without pulling in the entire QUIC stack.

quico will continue to use this TLS library internally, but separating it should make things cleaner, easier to maintain, and more broadly useful.

👉 What do you think about this move?

• Would a pure-JS TLS 1.3 library find real use cases on its own?
• Would you (or your projects) consider using it?
• Do you prefer everything kept together inside quico, or is splitting it cleaner?
• Any suggestions for what a standalone package should expose, or how it should be named/packaged?

Your feedback will help me shape this next step.
Thanks 🙏