Jim Schaad wrote:
>> I suggest writing:
>>
>> TLS 1.3 introduced early application data which is not used in EAP-TLS. A
>> server which receives an "early_data" extension MUST ignore the extension
>> or respond with a HelloRetryRequest as described in Section 4.2.10 of RFC
>> 8446.
>
> That is be
Noticed the following:
draft-ietf-emu-eap-tls13-04 defines the key hierarchy as
Type-Code= 0x0D
Key_Material = TLS-Exporter("EXPORTER_EAP_TLS_Key_Material",
Type-Code, 128)
IV = TLS-Exporter("EXPORTER_EAP_TLS_IV",
Thanks for your review, John. I agree with all the points and will address them
in a new version during the IETF week.
Jari
___
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu
Dear all,
We have a 2 hour session tomorrow (Monday, 25th March) morning between
09:00-11:00 in room Berlin/Brussels.
If you are presenting, please send us your slides by midnight tonight.
If you have any last minute updates to the slides, we can also try to
upload newer versions tomorrow morn
