On 21.10.25 11:09, Aijun Wang wrote:
There is a fundamental issue in the draft (see below). If you get a slot, please fix it//in your presentation.We are also applying the time slot for the presentation on the coming IETF 124 meeting.
There is big mismatch between what is in the text and what is in the proposed solution (figure 2). Text is saying 2x "TLS 1.3" and 2x "standard TLS 1.3 handshake" and RFC8446 is used as a normative reference, whereas figure 2 is using messages from TLS 1.2 which are not a part of "standard TLS 1.3 handshake". TLS 1.2 is never mentioned in the text and RFC5246 is also not used as a normative reference. Why is that the case?Wish to get your comments/suggestions on this topic before the meeting, and we can also discuss further during the on-site meeting.
Is there a good reason for using TLS 1.2 over TLS 1.3? If so, that should be explained in the draft.
Or did you intend to use TLS 1.3 but mistakenly used handshake messages from TLS 1.2?
-Usama
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
