[quicwg/base-drafts] Tweak the split between quic-transport and quic-tls drafts (#3717)

[David Schinazi <[e-mail]>]

Now that the drafts are not changing as much as they used to, it might be the right time to consider editorial efforts such as revisiting the current split between quic-transport and quic-tls. Let's imagine that once the RFCs ship, someone wants to build a version of QUIC with a custom handshake/key exchange protocol - they want to deviate as little as possible from QUICv1, but just want to swap TLS out for something else. Ideally, they would write a new draft that replaces quic-tls, and not change quic-transport at all. And in order to implement this, readers would not need to read quic-tls.

More specifically, I think we could accomplish this by moving the following sections from quic-tls to quic-transport:
* 5  Packet Protection (except 5.1 Packet Protection Keys)
* 6  Key Update (the interaction with the TLS key schedule would stay in quic-tls but the mechanisms to avoid deadlocks when discarding keys would move to quic-transport)
* 7  Security of Initial Messages

What do folks think? I could write up a PR to help make this happen but I'd like to get a sense of whether there's interest first.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3717