Hi,
I just looked at the presentation from the TLS session. My views:
- I think the order of P256 and MLKEM should be switched, irrespectively of
NIST's current discussion. Even if NIST do not change their current
specifications, I think long-term FIPS compliance is much more important then
sh
Issues
--
* tlswg/draft-ietf-tls-esni (+0/-0/💬4)
3 issues received 4 new comments:
- #630 Extraneous configurations MUST have invalid DNS names? (1 by seanturner)
https://github.com/tlswg/draft-ietf-tls-esni/issues/630
- #629 Should we recommend how often to rotate keys? (2 by enygre
> This vast difference between median and average indicates that a small
> fraction of data-heavy connections skew the average.
Hmmm. Why not describe this as "a large number of short sessions skew
the median, making the median fail to reflect total data usage"?
The total cost of all sessions is
On Sat, Nov 9, 2024, 1:34 AM John Mattsson wrote:
> Hi,
>
>
>
> I just looked at the presentation from the TLS session. My views:
>
>
>
> - I think the order of P256 and MLKEM should be switched, irrespectively
> of NIST's current discussion. Even if NIST do not change their current
> specificati
>
>
> > On average, around 15 million TLS connections are established with
> > Cloudflare per second. Upgrading each to ML-DSA, would take
> > 1.8Tbps, which is 0.6% of our current total network capacity. No
> > problem so far. The question is how these extra bytes affect
> > pe
