Message-
From: Alan DeKok
Date: Monday, 29 July 2019 at 00:51
To: Jim Schaad
Cc: Jouni Malinen , John Mattsson , EMU
WG
Subject: Re: [Emu] WGLC completed for for draft-ietf-emu-eap-tls13-05
On Jul 28, 2019, at 5:09 PM, Jim Schaad wrote:
>
> I cannot speak to PEAP, but it
On Jul 28, 2019, at 5:09 PM, Jim Schaad wrote:
>
> I cannot speak to PEAP, but it would seem that TEAP might need this feature
> as, at least on resumption, it is totally optional for both sides to use any
> TLVs an thus the same issue might be present. TTLS seems to always require
> that the cl
the
server based on a really fast read.
Jim
-Original Message-
From: Jouni Malinen
Sent: Sunday, July 28, 2019 12:58 PM
To: John Mattsson
Cc: Alan DeKok ; Jim Schaad
; EMU WG
Subject: Re: [Emu] WGLC completed for for draft-ietf-emu-eap-tls13-05
On Thu, Jul 25, 2019 at 10:49:40AM
On Thu, Jul 25, 2019 at 10:49:40AM +, John Mattsson wrote:
> Question: How will the use of Application data with TLSPlaintext.fragment =
> 0x00 work with EAP-TTLS, PEAP, and TEAP when they start using TLS 1.3? I
> assume they will need to send the same 0x00 to commit to not sending any more
for draft-ietf-emu-eap-tls13-05
Hi,
Based on the discussion on the list and at the meeting today I suggest the
following changes to Section 2.1, 2.5, and figures. When we agree I will make a
commit to GitHub and submit a new version of the draft.
With the solution suggeste
Hi,
Based on the discussion on the list and at the meeting today I suggest the
following changes to Section 2.1, 2.5, and figures. When we agree I will make a
commit to GitHub and submit a new version of the draft.
With the solution suggested by Jim, there should be no need to force
NewSession
On Jul 13, 2019, at 4:21 PM, Jouni Malinen wrote:
> I'm not sure how I'd feel about EAP-TLS extension that uses actual
> application data when we have EAP-TEAP available for cases that need
> additional data to be exchanged in the tunnel.
Sure.
> Anyway, this combination
> of server sending on
On Sat, Jul 13, 2019 at 08:59:04AM +0200, Alan DeKok wrote:
> On Jul 12, 2019, at 11:08 PM, Jouni Malinen wrote:
> > It would seem to make sense to me to allow the EAP-TLS 1.3 server to
> > send out either an empty plaintext or a one octet plaintext to avoid
> > this issue in a straightforward man
On Jul 12, 2019, at 11:08 PM, Jouni Malinen wrote:
> In other words, there does not seem to be any convenient way of
> implementing this with the current version of one of the most commonly
> used TLS libraries. I can make this work by sending out a one-octet
> (0x00) TLSPlaintext as a workaround,
On Wed, Jun 26, 2019 at 09:16:19PM -0700, Joseph Salowey wrote:
> The Working Group last call has completed with no comments for
> draft-ietf-emu-eap-tls13-05. I would like to confirm that some working
> group members have reviewed the draft. If you have reviewed the draft
> please respond to thi
There have been several reviews of different aspects of this draft in the past:
Jim provided a complete review here:
https://mailarchive.ietf.org/arch/msg/emu/ZDwpgyOL5eBPgyOGwXqxj1VhX-4
A discussion about the L-bit and fragmentation here:
https://mailarchive.ietf.org/arch/msg/emu/ZexFr7GROnvNO
The Working Group last call has completed with no comments for
draft-ietf-emu-eap-tls13-05. I would like to confirm that some working
group members have reviewed the draft. If you have reviewed the draft
please respond to this thread.
THanks,
Joe
___
12 matches
Mail list logo
