On 30.01.26 14:25, Aijun Wang wrote:
We will refine the draft in the coming days which will try to address your comments.
Thanks. Here is a structure that would help me to help you :)
1. Introduction
* Problem statement: Say in general what the problem is. IMHO this
should *not* include CATS. Anyone unfamiliar with CATS should be
able to understand your problem.
2. Terminology
* Define any terms not defined in RFC8446bis
3. Motivation and design rationale
* I really like how Russ motivates the problem statement in
RFC8773bis [0]. Use it as a sample.
* Here you should address all the concerns from WG, including
justification with compelling arguments and authentic references
why you think it should be done within TLS handshake.
* You could put CATS here as a motivational use case.
4. Proposed solution (one or more sections)
* Protocol design with protocol diagram (Use TLS 1.3 /only/)
5. Security considerations
1. Threat model
2. Desired security goals
3. Other security implications/considerations
Hope it helps.
You may also find [1] helpful. I will update it in the next weeks with
more details.
-Usama [0] https://www.ietf.org/archive/id/draft-ietf-tls-8773bis-13.html#section-3[1] https://www.ietf.org/archive/id/draft-usama-tls-fatt-extension-01.html#section-4
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
