Dear all,
Sorry for the radio silence. I have over-committed myself to too many things. I
think I have now read the entire discussion on OCSP.
EAP-TLS with TLS 1.3 is a working group document so the text will reflect
whatever the working group wants. The authors and contributors are at the
ser
Hi Stefan,
I made a minor update to reflect your feedback
(https://github.com/emu-wg/eaptls-longcert/compare/3ac0a18..2093026):
Thus, the AIA extension can reduce the size of the certificate chain by only
including a pointer to the issuer certificate instead of including the entire
issuer cert
Hi Hannes,
Thanks. I have opened several issues on github based on your review:
https://github.com/emu-wg/draft-ietf-emu-eap-tls13/issues
--Mohit
On 10/21/20 11:55 AM, Hannes Tschofenig wrote:
Hi all,
Roman asked me to look at draft-ietf-emu-eap-tls13-11.
I have carefully read through the
Hi Hannes,
Jim Schaad had asked for this:
https://mailarchive.ietf.org/arch/msg/emu/XpRkNN-mh5BuiTD1O8iEfz9sM4M/
It is still optional to use. The figure only shows what the exchange would look
like if a HRR was sent by the server.
--Mohit
On 10/21/20 12:16 PM, Hannes Tschofenig wrote:
Hi all,
Hi Hannes,
This text and guidance was specifically requested by working group members like
Alan. Unless the text is wrong, I don't see any point in removing it. Other
TLS-based EAP methods are obviously free to use parts of this text relevant to
them. Note that their resumption and authorizatio
I think that is great!
Stefan Santesson
From: Mohit Sethi M
Date: Saturday, 31 October 2020 at 15:19
To: Stefan Santesson , Mohit Sethi M
, Benjamin Kaduk
Cc: "last-c...@ietf.org" ,
"draft-ietf-emu-eaptlscert@ietf.org"
, "emu@ietf.org" ,
"sec...@ietf.org"
Subject: Re: [Emu] Secd
