On Jul 8, 2021, at 12:42 PM, Joseph Salowey wrote:
>
> I created PR that I think captures these suggestions and another editorial
> fix - https://github.com/emu-wg/draft-ietf-emu-eap-tls13/pull/87
I think it looks good.
Alan DeKok.
___
Emu
I created PR that I think captures these suggestions and another editorial
fix - https://github.com/emu-wg/draft-ietf-emu-eap-tls13/pull/87
Cheers,
Joe
On Thu, Jul 8, 2021 at 9:36 AM Oleg Pekar wrote:
>
>
> On Thu, Jul 8, 2021 at 8:31 AM Mohit Sethi M
> wrote:
>
>> Hi Oleg, Joe, all,
>> On
On Thu, Jul 8, 2021 at 8:31 AM Mohit Sethi M
wrote:
> Hi Oleg, Joe, all,
> On 7/8/21 8:06 AM, Joseph Salowey wrote:
>
>
>
> On Tue, Jul 6, 2021 at 10:08 PM Joseph Salowey wrote:
>
>>
>>
>> On Mon, Jun 28, 2021 at 8:11 AM Oleg Pekar
>> wrote:
>>
>>> I still see unclearness in Section "2.2.
On Thu, Jul 8, 2021 at 6:11 AM Alan DeKok wrote:
> On Jul 8, 2021, at 2:52 AM, tom.ri...@securew2.com wrote:
> > Maybe this has been discussed already, but we often see the need for
> multiple root cas when people are migrating the root CA of their RADIUS
> server. They would then configure both
On Jul 8, 2021, at 2:52 AM, tom.ri...@securew2.com wrote:
> Maybe this has been discussed already, but we often see the need for multiple
> root cas when people are migrating the root CA of their RADIUS server. They
> would then configure both the old and new Root CA in the client to allow
>
their RADIUS server. They
would then configure both the old and new Root CA in the client to allow
seamless transition.
Thanks,
Tom
SecureW2
From: Emu On Behalf Of Mohit Sethi M
Sent: Thursday, July 8, 2021 7:31 AM
To: Joseph Salowey ; Oleg Pekar
Cc: EMU WG
Subject: Re: [Emu] WG Last Call
Hi Oleg, Joe, all,
On 7/8/21 8:06 AM, Joseph Salowey wrote:
On Tue, Jul 6, 2021 at 10:08 PM Joseph Salowey
mailto:j...@salowey.net>> wrote:
On Mon, Jun 28, 2021 at 8:11 AM Oleg Pekar
mailto:oleg.pekar.2...@gmail.com>> wrote:
I still see unclearness in Section "2.2. Identity Verification",
On Tue, Jul 6, 2021 at 10:08 PM Joseph Salowey wrote:
>
>
> On Mon, Jun 28, 2021 at 8:11 AM Oleg Pekar
> wrote:
>
>> I still see unclearness in Section "2.2. Identity Verification", I'm
>> trying to look from the implementer's perspective.
>>
>> 1) "Since EAP-TLS deployments may use more than
On Mon, Jun 28, 2021 at 8:11 AM Oleg Pekar
wrote:
> I still see unclearness in Section "2.2. Identity Verification", I'm
> trying to look from the implementer's perspective.
>
> 1) "Since EAP-TLS deployments may use more than one EAP
>server, each with a different certificate, EAP peer
I still see unclearness in Section "2.2. Identity Verification", I'm trying
to look from the implementer's perspective.
1) "Since EAP-TLS deployments may use more than one EAP
server, each with a different certificate, EAP peer implementations
SHOULD allow for the configuration of a unique
This is the working group last-call (WGLC) for draft-ietf-emu-eap-tls13.
Please review the draft, focus on the changes since the last WGLC and
submit your comments to the list by July 8, 2021.
The IETF datatracker status page for this draft is:
On May 16, 2021, at 2:30 PM, Joseph Salowey wrote:
> This is under-stating the issue rather severely. We know with
> absolute certainty that most (if not all) EAP implementations and
> access networks limit the number of EAP packet exchanges. Perhaps
> update the text to reference
On Thu, May 6, 2021 at 12:11 PM Alan DeKok
wrote:
>
>
> > On May 5, 2021, at 11:33 AM, Joseph Salowey wrote:
> >
> > This is the working group last-call for draft-ietf-emu-eap-tls13.
> Please review the draft, focus on the recent changes and submit your
> comments to the list by May 20, 2021.
>
: Re: [Emu] WG Last Call for Using EAP-TLS with TLS 1.3
I have noticed that there is one modification in the Figure 1 flow diagram of
edition 15.
edition 14 has TLS close_notify message, but in edition 15 changed into TLS
application Data 0x00.
in the section 2.1.1, it says" TLS application
e messages?
another question: what's the format of the EAP-success measge, plaintext ot
ciphertext?
Best Regards,
Meiling
From: Joseph Salowey
Date: 2021-05-05 23:33
To: EMU WG
Subject: [Emu] WG Last Call for Using EAP-TLS with TLS 1.3
This is the working group last-call for draft-ietf-emu-eap-tls1
whether
the draft-13 exporter is livable.
Jorge Vergara
From: Joseph Salowey
Sent: Friday, May 7, 2021 2:19 PM
To: Jorge Vergara
Cc: Alan DeKok ; EMU WG
Subject: Re: [Emu] WG Last Call for Using EAP-TLS with TLS 1.3
On Fri, May 7, 2021 at 1:09 PM Jorge Vergara
mailto:jover...@microsoft.com>
On May 7, 2021, at 5:18 PM, Joseph Salowey wrote:
> [Joe] I think the one issue that was raised during TLS review was that using
> the same label for MSK and EMSK could make it more difficult to separate out
> the derivations of these keys at the TLS level. For example, example,
> perhaps the
AP method implementation from scratch. The more guidance toward
> this goal that can be included in the document the better, in my opinion.
>
>
[Joe] Thanks, having a more voices chime in on issues can help resolve them
more quickly and satisfactorily.
> Jorge
>
> -----Original Me
On May 7, 2021, at 4:09 PM, Jorge Vergara wrote:
> The Windows implementation is using draft-13 exporters; it is not possible to
> change at this point unless a critical technical issue that prevents
> functionality or impacts security were to be discovered. I don't think this
> is such an
n my opinion.
Jorge
-Original Message-
From: Emu On Behalf Of Alan DeKok
Sent: Thursday, May 6, 2021 12:12 PM
To: Joseph Salowey
Cc: EMU WG
Subject: Re: [Emu] WG Last Call for Using EAP-TLS with TLS 1.3
> On May 5, 2021, at 11:33 AM, Joseph Salowey wrote:
>
> This is the wor
> On May 5, 2021, at 11:33 AM, Joseph Salowey wrote:
>
> This is the working group last-call for draft-ietf-emu-eap-tls13. Please
> review the draft, focus on the recent changes and submit your comments to the
> list by May 20, 2021.
Section 1 says:
While this document updates
This is the working group last-call for draft-ietf-emu-eap-tls13. Please
review the draft, focus on the recent changes and submit your comments to
the list by May 20, 2021.
Thanks,
Joe
The IETF datatracker status page for this draft is:
22 matches
Mail list logo
