Thanks, Mohit, for the quick turn-over.
From: Mohit Sethi M
Sent: Monday, November 2, 2020 12:21 PM
To: Hannes Tschofenig ; Mohit Sethi M
; emu@ietf.org
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: Conformance with the TLS 13 Spec
Done as suggested:
https://github.com/emu-wg/draft-ietf
..@ericsson.com>;
emu@ietf.org<mailto:emu@ietf.org>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: Conformance with the TLS 13 Spec
I now understand your issue with the sentence "An EAP-TLS peer and server
SHOULD support the use of HelloRetryRequest message.". I guess there is
; Mohit Sethi M
; emu@ietf.org
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: Conformance with the TLS 13 Spec
I now understand your issue with the sentence "An EAP-TLS peer and server
SHOULD support the use of HelloRetryRequest message.". I guess there is no need
for it, i.e., t
:mohit.m.se...@ericsson.com>
Sent: Saturday, October 31, 2020 6:04 PM
To: Hannes Tschofenig
<mailto:hannes.tschofe...@arm.com>;
emu@ietf.org<mailto:emu@ietf.org>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: Conformance with the TLS 13 Spec
Hi Hannes,
Jim Schaad had asked f
enig ; emu@ietf.org
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: Conformance with the TLS 13 Spec
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
lik
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
Hi all,
Section 2.1.6 says:
"
An EAP-TLS peer and server SHOULD support the use of
HelloRetryRequest message.
"
My understanding of the TLS 1.3 specification is that the HelloRetryRequest is
not an optional-to-implement message but it is only optional to use.
Is there a reason to