Hi Bernard,
Thanks for your comments on backward compatibility. I think PR #83 addresses
your comments. I did not write anything about TLS 1.0 and TLS 1.1 as RFC 8996
(which updates RFC 5216) formally forbids support and negotiation of these weak
versions.
https://github.com/emu-wg/draft-ietf-
On Jun 18, 2021, at 5:23 PM, John Mattsson wrote:
> Joe: How about:
> "[4] Cryptographic Negotiation: The TLS layer handles the negotiation of
> cryptographic parameters. When EAP-TLS is used with TLS 1.3, EAP-TLS inherits
> the cryptographic negotiation of AEAD algorithm, HKDF hash algorithm, k
On Jun 18, 2021, at 4:30 PM, Joseph Salowey wrote:
> [Joe] The github PRs make it easier to view the changes in the context of
> the document. I realize there may be a little bit of extra work to associate
> the changes to the issues, but this should be too difficult to do.
It's also not
Hi Alan,
Thanks for your thorough review of version -16. Based on the suggested changes
Joe made in GitHub issue #83, I have made commits to PR #83.
https://github.com/emu-wg/draft-ietf-emu-eap-tls13/issues/84
https://github.com/emu-wg/draft-ietf-emu-eap-tls13/pull/83
Below is a summary of
On Thu, Jun 17, 2021 at 9:55 AM Alan DeKok
wrote:
> On Jun 17, 2021, at 12:04 PM, John Mattsson
> wrote:
> > I have made a single PR addressing all the currently listed issues in
> the way suggested by Joe.
> >
> > https://github.com/emu-wg/draft-ietf-emu-eap-tls13/pull/83/files
> >
> > - Does P
