I am just finally getting caught up on mail for the EMU WG and am getting
this done.
It should probably be clarified that Figure 1has the additional restriction
that the server is not sending any resumption tickets as well.It would
also be better to label the TLS Application Data as the
Hi,
I read the whole document again. I think it is in a good shape. Some quick high
level comments. I will do a more detailed review(s) later
- I think this should formally update rfc5448bis
- "This specification is an optional extension to the EAP-AKA'"
While the extension is not
The did not get any feedback on the suggested changes I send out on Thu, 25
July 2019 so I submitted that version as -06 that addresses all the comments
made during the WGLC.
Cheers,
John
-Original Message-
From: Emu on behalf of "internet-dra...@ietf.org"
Reply to: "emu@ietf.org"
Then draft-dekok-emu-tls-eap-types will have to describe how TLS-based EAP
types do or not do the commit with application data.
As far as I understand, 0x00 will work for these other EAP types as well, so
not need to change any thing in draft-ietf-emu-eap-tls13.
Cheers,
John
-Original
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the EAP Method Update WG of the IETF.
Title : Using EAP-TLS with TLS 1.3
Authors : John Mattsson
Mohit Sethi
Filename
