[TLS] Re: I-D Action: draft-denis-tls-aegis-03.txt

Hi, Looking at the performance figures for the X2 and X4 variant of AEGIS on AMD Zen 4 and Apple M1, I started thinking if adding parallelism at the algorithm level is the right solution. An alternative is to add parallelism at the protocol level similar to IPsec, something DTLS 1.3 and QUIC do

[TLS] Re: Working Group Last Call for TLS 1.2 is in Feature Freeze

I think it's ready for publication. On Tuesday, 3 December 2024 22:26:30 CET, Sean Turner wrote: This is the working group last call for TLS 1.2 is in Feature Freeze. Please review draft-ietf-tls-tls12-frozen [1] and reply to this thread indicating if you think it is ready for publication or n

[TLS] Re: draft-connolly-tls-mlkem-key-agreement

On Saturday, 7 December 2024 23:32:03 CET, D. J. Bernstein wrote: Watson Ladd writes: Having MLKEM without a hybrid as an option in TLS when the interoperable choice is a hybrid Some previous messages claim that there's a split between customers demanding hybrids and customers demanding non-hy

[TLS] Re: draft-connolly-tls-mlkem-key-agreement

+1 for adoption While I'm stronly against wide deployment of pure ML-KEM at this moment in time, I'm very much in favour of adoption of this document, having stable definitions for such codepoints, even if they will get doployed only in closed networks is still useful. On Thursday, 5 December 20

[TLS] I-D Action: draft-ietf-tls-tls12-frozen-03.txt

Internet-Draft draft-ietf-tls-tls12-frozen-03.txt is now available. It is a work item of the Transport Layer Security (TLS) WG of the IETF. Title: TLS 1.2 is in Feature Freeze Authors: Rich Salz Nimrod Aviram Name:draft-ietf-tls-tls12-frozen-03.txt Pages: 5 Dates

[TLS] Re: I-D Action: draft-ietf-tls-tls12-frozen-03.txt

This draft incorporates feedback from: Rob Sayre John Mattson Bas Wasterbaan David Benjamin I also changed the 8447 reference to the 8447-bis draft. On 12/9/24, 3:30 PM, "internet-dra...@ietf.org " mailto:internet-dra...@ietf.org>

[TLS] Re: draft-connolly-tls-mlkem-key-agreement

Pursuant to this thread, preliminary support for MLKEM768-only has been merged into rustls (I contributed): https://github.com/rustls/rustls/pull/2259 On Thu, Dec 5, 2024 at 4:10 PM Scott Fluhrer (sfluhrer) wrote: > How do we proceed with this draft? > > > > This draft is quite boring (which is

[TLS] Re: Working Group Last Call for TLS 1.2 is in Feature Freeze

Just a reminder that this WG last call is still ongoing. spt > On Dec 3, 2024, at 16:26, Sean Turner wrote: > > This is the working group last call for TLS 1.2 is in Feature Freeze. Please > review draft-ietf-tls-tls12-frozen [1] and reply to this thread indicating if > you think it is ready

[TLS] Re: [EXT] Re: draft-connolly-tls-mlkem-key-agreement

+1 for adoption While I'm stronly against wide deployment of pure ML-KEM at this moment in time, I'm very much in favour of adoption of this document, having stable definitions for such codepoints, even if they will get doployed only in closed networks is still useful. +1 for adoption. And I am

[TLS] Secdir last call review of draft-ietf-tls-svcb-ech

Reviewer: Tirumaleswar Reddy K Review result: Ready with issues I have reviewed this document as part of the SEC area directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the Security area directors. Docume