Based on this description TLS WG would not be the right venue for this draft. The way this would work is that whatever WG was working on this draft would coordinate with TLS WG.
I concur. This seems to be mainly about changing HTTP (and using those changes to cause the TLS runtime to do things), so perhaps the HTTP working group is a good place to start, https://datatracker.ietf.org/wg/httpbis/about/
_______________________________________________ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org