Hi Mohit,
See below. Thanks for your super quick response.
From: Mohit Sethi M
Sent: Tuesday, June 16, 2020 12:25 PM
To: Hannes Tschofenig ; Mohit Sethi M
; emu@ietf.org
Subject: Re: [Emu] Commitment Message in draft-ietf-emu-eap-tls13
Hi Hannes,
On 6/16/20 12:37 PM, Hannes Tschofenig wrote
Tschofenig ; Mohit Sethi M
; emu@ietf.org
*Subject:* Re: [Emu] Commitment Message in draft-ietf-emu-eap-tls13
Hi Hannes,
On 6/16/20 12:37 PM, Hannes Tschofenig wrote:
Hi Mohit,
I had a chance to read through the emails you provided. A good
discussion.
I can offer three solutions
:* Monday, June 15, 2020 3:52 PM
*To:* Hannes Tschofenig ; emu@ietf.org
*Subject:* Re: [Emu] Commitment Message in draft-ietf-emu-eap-tls13
Hi Hannes,
Unfortunately you are wrong here. The design decision was in fact
taken to avoid changes to the underlying TLS implementation while also
avoiding
the encryption layer
(after successfully establishing it) to send a plaintext message.
Ciao
Hannes
From: Mohit Sethi M
Sent: Monday, June 15, 2020 3:52 PM
To: Hannes Tschofenig ; emu@ietf.org
Subject: Re: [Emu] Commitment Message in draft-ietf-emu-eap-tls13
Hi Hannes,
Unfortunately you
Message in draft-ietf-emu-eap-tls13
Hi Hannes,
Unfortunately you are wrong here. The design decision was in fact taken to
avoid changes to the underlying TLS implementation while also avoiding changes
to RFC 3748. To summarize:
Jouni Malinen pointed out that mapping session resumption of TLS 1.3
Hi Hannes,
Unfortunately you are wrong here. The design decision was in fact taken to
avoid changes to the underlying TLS implementation while also avoiding changes
to RFC 3748. To summarize:
Jouni Malinen pointed out that mapping session resumption of TLS 1.3 to EAP-TLS
is non-trivial. See
Hi all,
This has probably been discussed extensively in the EMU group. I am sorry to
bring it up again but I believe this is a bad design decision. I raised it in
my short review just sent to the list but I believe it is worthwhile to point
it out separately.
draft-ietf-emu-eap-tls13
