Hi Meiling, In version 15 the group decided to go back more or less to how things worked in version 13 where protected TLS application Data 0x00 is send instead of close_notify. This is changed in a lot of places in the draft.
A big change from -13 is that where protected TLS application Data 0x00 is not a protected success indication as defined in RFC 3748. That the server only sends EAP-success after this follow from it being a protected success indication. When reading through the document to write this answer I saw that there was some leftover from the commitment message still in the draft. I made a PR to address this. https://github.com/emu-wg/draft-ietf-emu-eap-tls13/pull/69 EAP-success is not encrytpted in any way. It is defined in RFC 3748. Cheers, John From: Emu <[email protected]> on behalf of Meiling Chen <[email protected]> Date: Saturday, 8 May 2021 at 10:25 To: Joseph Salowey <[email protected]>, emu <[email protected]> Subject: Re: [Emu] WG Last Call for Using EAP-TLS with TLS 1.3 I have noticed that there is one modification in the Figure 1 flow diagram of edition 15. edition 14 has TLS close_notify message, but in edition 15 changed into TLS application Data 0x00. in the section 2.1.1, it says" TLS application data 0x00 is therefore to be interpreted as success after the EAP-Request that contains TLS application data 0x00. After the EAP-TLS server has received an empty EAP-Response to the EAP-Request containing the TLS application data 0x00, the EAP-TLS server sends EAP-Success." is the data 0x00 that mean not send any more handshake messages? another question: what's the format of the EAP-success measge, plaintext ot ciphertext? Best Regards, Meiling From: Joseph Salowey<mailto:[email protected]> Date: 2021-05-05 23:33 To: EMU WG<mailto:[email protected]> Subject: [Emu] WG Last Call for Using EAP-TLS with TLS 1.3 This is the working group last-call for draft-ietf-emu-eap-tls13. Please review the draft, focus on the recent changes and submit your comments to the list by May 20, 2021. Thanks, Joe The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-emu-eap-tls13/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-emu-eap-tls13-15 https://datatracker.ietf.org/doc/html/draft-ietf-emu-eap-tls13-15 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-emu-eap-tls13-15
_______________________________________________ Emu mailing list [email protected] https://www.ietf.org/mailman/listinfo/emu
