> So we can't use the legacy_session_id_echo of SH. We only need client to carry ECH, right? So server just need to simply repeat what Session ID it received in Client Hello. 11.09.2024, 17:45, "涛叔" :According to https://datatracker.ietf.org/doc/html/rfc8446#section-4.1.3A client which receives a l
Internet-Draft draft-ietf-tls-tlsflags-14.txt is now available. It is a work
item of the Transport Layer Security (TLS) WG of the IETF.
Title: A Flags Extension for TLS 1.3
Author: Yoav Nir
Name:draft-ietf-tls-tlsflags-14.txt
Pages: 9
Dates: 2024-09-13
Abstract:
A nu
The following errata report has been verified for RFC9147,
"The Datagram Transport Layer Security (DTLS) Protocol Version 1.3".
--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid8100
--
Status:
I want to thank everyone for your feedback. It's been super helpful.
I think I should elaborate on what the problem is and how it can be fixed.
I've worked with a lot of companies who want to use mTLS (as bas as the
name is) to increase security but don't know how to do it in a way that
won't red
On Fri, Sep 13, 2024 at 08:08:12PM -0700, Mark Robinson wrote:
> I want to thank everyone for your feedback. It's been super helpful.
>
> I think I should elaborate on what the problem is and how it can be fixed.
>
> I've worked with a lot of companies who want to use mTLS (as bas as the
> name
