On Mar 25, 2019, at 12:59 AM, John Mattsson wrote:
>
> 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
https://tools.ietf.org/html/draft-sy-tls-resumption-group
This document will be discussed today in the TLS WG 11.20 - 12.20. Might be
interesting for the discussion on cross method resumption for TLS-based EAP
methods.
Cheers,
John
___
Emu mailing
On Mar 25, 2019, at 5:36 AM, John Mattsson wrote:
>
> https://tools.ietf.org/html/draft-sy-tls-resumption-group
>
> This document will be discussed today in the TLS WG 11.20 - 12.20. Might be
> interesting for the discussion on cross method resumption for TLS-based EAP
> methods.
I took a q
For those who are interested, we will be continuing our IoT Onboarding
discussion Wednesday @ 2:00pm in Karlin 3. Topics will include review of the
various onboarding mechanisms that we listed on Github, review of the questions
we were asking, some live editing of THAT, and some mapping of all
Hi,
I have several questions about TEAP TLS session resume since I am not sure
I succeeded to interpret the relevant sections of RFC 7170 and RFC 5077
correctly.
1) Does it make sense for TEAP server to support both TLS session resume
using server state and TLS session resume using PAC? Should t