On Sep 22, 2020, at 10:35 AM, John Mattsson wrote:
>
> If we are going back to an encrypted application message with 0x00, how do we
> update the draft to make it clear that the commitment message is encrypted?
> Several people understood that 0x00 was supposed to not be encrypted. Is
> someth
on , Mohit Sethi M
, Benjamin Kaduk , EMU WG
Subject: Re: [Emu] Commitment Message handling in EAP-TLS 1.3
On Sep 17, 2020, at 12:44 PM, Jorge Vergara wrote:
>
> Does anyone else have any other thoughts on this? I'm not a TLS expert but
> similarly value the TLS Fatal Alerts over u
On Sep 17, 2020, at 12:44 PM, Jorge Vergara wrote:
>
> Does anyone else have any other thoughts on this? I'm not a TLS expert but
> similarly value the TLS Fatal Alerts over using close_notify. If we will be
> losing alerts then I would favor switching back to 0x00.
In the absence of further
ember 2, 2020 10:33 AM
To: John Mattsson
Cc: John Mattsson ; Mohit Sethi M
; Jorge Vergara
; Mohit Sethi M ; Benjamin
Kaduk ; EMU WG
Subject: Re: [Emu] Commitment Message handling in EAP-TLS 1.3
On Sep 1, 2020, at 10:23 AM, John Mattsson wrote:
>
> If the ability to send a descriptiv
On Sep 1, 2020, at 10:23 AM, John Mattsson wrote:
>
> If the ability to send a descriptive TLS Fatal Alert back to the peer is a
> requirement, changing to close_notify seems like a bad idea.
It's fine for EAP Success. But having two different code paths is a little
surprising.
> My unders
ge Vergara
, Mohit Sethi M , Benjamin
Kaduk , EMU WG
Subject: Re: [Emu] Commitment Message handling in EAP-TLS 1.3
On Sep 1, 2020, at 8:24 AM, John Mattsson
wrote:
> Reading up on the mail discussion more (I have been on parental leave), I
don't see any real motivation for this l
On Sep 1, 2020, at 8:24 AM, John Mattsson wrote:
> Reading up on the mail discussion more (I have been on parental leave), I
> don't see any real motivation for this late technical change suggestion...
My $0.02 is that it's philosophical. EAP-TLS does authentication using TLS.
Adding an ext
ient
authentication.
Cheers,
John
-Original Message-
From: Emu on behalf of John Mattsson
Date: Tuesday, 1 September 2020 at 10:10
To: Mohit Sethi M , Alan DeKok
, Jorge Vergara
Cc: Mohit Sethi M , Benjamin Kaduk ,
EMU WG
Subject: Re: [Emu] Commitment Message handling in EAP-TLS 1.3
: Mohit Sethi M , Benjamin Kaduk ,
EMU WG
Subject: Re: [Emu] Commitment Message handling in EAP-TLS 1.3
I seem to agree with the consensus around the usage of close_notify
instead of a byte of 0x00. In fact, I can't even remember the reason for
that choice anymore.
The draf
I seem to agree with the consensus around the usage of close_notify
instead of a byte of 0x00. In fact, I can't even remember the reason for
that choice anymore.
The draft is now updated in github to specify the usage of close_notify:
https://github.com/emu-wg/draft-ietf-emu-eap-tls13
Here is t
Hi Mohit,
Sorry for the slow response.
On Fri, Jul 31, 2020 at 02:08:44PM +, Mohit Sethi M wrote:
> Dear all,
>
> Thanks all for the discussion on the commitment message.
>
> draft-ietf-emu-eap-tls13-10
> (https://tools.ietf.org/html/draft-ietf-emu-eap-tls13-10) in figure 2 shows
> the ti
: Alan DeKok
Sent: Tuesday, August 4, 2020 10:16 AM
To: Jorge Vergara
Cc: Jim Schaad ; Mohit Sethi M
; EMU WG ; Benjamin Kaduk
Subject: Re: [Emu] Commitment Message handling in EAP-TLS 1.3
On Aug 3, 2020, at 2:23 PM, Jorge Vergara wrote:
>
> ACK that EAP-TLS does not need to keep the conn
On Aug 3, 2020, at 2:23 PM, Jorge Vergara wrote:
>
> ACK that EAP-TLS does not need to keep the connection open.
I agree. I'm happy to change the implementations to send "close notify".
> Question: should some consideration be given to consistency with other EAP
> methods that do need to ke
, August 1, 2020 8:23 AM
To: 'Alan DeKok'
Cc: 'Mohit Sethi M' ; 'EMU WG' ;
'Benjamin Kaduk'
Subject: Re: [Emu] Commitment Message handling in EAP-TLS 1.3
-Original Message-
From: Alan DeKok
Sent: Saturday, August 1, 2020 6:53 AM
To: Jim Schaa
-Original Message-
From: Alan DeKok
Sent: Saturday, August 1, 2020 6:53 AM
To: Jim Schaad
Cc: Mohit Sethi M ; EMU WG ; Benjamin
Kaduk
Subject: Re: [Emu] Commitment Message handling in EAP-TLS 1.3
On Jul 31, 2020, at 12:30 PM, Jim Schaad wrote:
>
> Ok – so this issue was rai
On Jul 31, 2020, at 12:30 PM, Jim Schaad wrote:
>
> Ok – so this issue was raised at IETF 102. (presentation
> https://www.ietf.org/proceedings/102/slides/slides-102-emu-eap-tls-with-tls-13-00)
>
> Just reading the slides is not telling me what was the problem. I think I am
> going to need
Ok – so this issue was raised at IETF 102. (presentation
https://www.ietf.org/proceedings/102/slides/slides-102-emu-eap-tls-with-tls-13-00)
Just reading the slides is not telling me what was the problem. I think I am
going to need to hear the audio of the presentation. I have an extremely
17 matches
Mail list logo
