On Tue, Oct 25, 2022 at 02:57:47PM +1100, Martin Thomson wrote:
>
> Removing HRR might be possible if we look at putting more stuff in
> DNS or something along those lines, but that would require a bunch
> of care and preparation. That's effort that - at least to me -
> might be better spent els
>
> OK, that's more than I expected, although I kind of wonder what
> combinations are doing this.
>
It varies a bit over time, but today most were caused by a certain client
sending a P-384 keyshare while also announcing support for P-256.
On the other hand, most clients today send x25519 key s
On Thu, Oct 27, 2022, at 00:01, Ilari Liusvaara wrote:
> Idea
We're not short on ideas (your idea is not new). We're short on the
willingness to implement and deploy them.
___
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
On Thu, Oct 27, 2022, at 09:23, Martin Thomson wrote:
> On Thu, Oct 27, 2022, at 00:01, Ilari Liusvaara wrote:
>> Idea
>
> We're not short on ideas (your idea is not new). We're short on the
> willingness to implement and deploy them.
I should apologize here. Ilari's idea is - I think - a relat
Hiya,
This is a "just wondering" type email...
On 26/10/2022 23:32, Martin Thomson wrote:
harder part: getting people interested in deploying a fix.
If ECH+PQ-hybrid turns out to be problematic (size-wise) and
PQ-hybrid by itself increases occurrences of HRR, and if ECH
is generally desirabl
