The IESG has received a request from the Transport Layer Security WG (tls) to
consider the following document: - 'Importing External PSKs for TLS'
as Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive
On Thu, Oct 1, 2020 at 7:05 AM Michael D'Errico wrote:
> > I am having a difficult time understanding the tradeoffs you're facing.
>
> This is the first time I'm reading the TLS 1.3 RFC. I have
> implemented SSLv3, TLS 1.0, 1.1, and 1.2. You may have
> used my test server at https www dot mikes
Hi!
I've assumed the role of responsible AD on this document. As such, I performed
an AD review of draft-ietf-tls-external-psk-importer-05. All in all, it is in
good shape. My feedback is primarily around clarifying the content of the new
KDF registry and a few of editorial suggestions. Giv
> I am having a difficult time understanding the tradeoffs you're facing.
This is the first time I'm reading the TLS 1.3 RFC. I have
implemented SSLv3, TLS 1.0, 1.1, and 1.2. You may have
used my test server at https www dot mikestoolbox dot
org or dot net to test your own code. It's kind of ol
> Not always; see TCP "fast open" options.
>Maybe this should be disabled? Fortunately if you wanted
to there is a setsockopt for TCP_FASTOPEN.
Yeah, that will go over great for the folks who want to DDoS you. :)
___
TLS mailing list
TLS@
