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

[Mike Bishop <[e-mail]>]

Looking at what would be entailed, my first instinct was to try slotting it into new subsections of Section 12.1.  However, that makes the TOC deeper than is ideal and would probably require more editorial fine-tuning to get right.  If you want to pursue this, I think the fastest path to coherency is to make a new top-level section at the end of the document on Packet Protection and just adjust the cross-references to be forward-references there.

Then:
- New text on the values supplied by TLS (packet protection keys, header protection keys, ability to generate new keys on demand) in a subsection of TRANS-7
- Move TLS-5.0 into TRANS-(new).0
- Retain TLS-5.1 and TLS-5.2 in TLS
- Split TLS-5.3, moving the "how to apply selected AEAD and key" into TRANS-(new).1
- Move most of TLS-5.4 through TLS-5.6 into subsections of TRANS-(new), leaving only the key derivation in TLS
- TLS-5.7 should mostly move to a subsection of TRANS-13.1, but some TLS specifics would need to be abstracted out
- TLS-5.8 should move under TRANS-(new)
- TLS-7 should move under TRANS-(new), possibly removing specific references to TLS and discussing tampering with the cryptographic handshake generically.

TLS-6 is trickier.  The mechanics of how to perform a key update on the wire need to move, probably to the final subsection of TRANS-(new); the mechanics of how to obtain the new key need to remain in TLS.  These aren't currently clearly separated, and might require some additional text to abstract them.

-- 
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#issuecomment-694900675