Hi All,
Thank you for this interesting draft, I had a couple of quick questions.
OpenSSL has been mentioned in this thread, but I was wondering if you had
examples of other implementations or services that use the "key_share first"
algorithm outlined in Section 3.1 of the draft, so that as th
It's OK, just appeared on the admin page.
The Uni email can be pretty messed up sometimes so whenever things seem to take
too long I check that they're actually still working. All fine, as you were
:-).
Peter.
From: TLS on behalf of Michael P1
Sent
Responses inline.
On Fri, Oct 27, 2023 at 5:04 AM Michael P1 wrote:
> Hi All,
>
> Thank you for this interesting draft, I had a couple of quick questions.
>
> OpenSSL has been mentioned in this thread, but I was wondering if you had
> examples of other implementations or services that use the "k
This is a good document and should be adopted. I have a mild preference for a
separate document because I think it is important to keep this separate from
8446 because it would require less work (at least in the doc review aspect) for
programmers to fix, and I am worried that it would “get lost”
On Fri, Oct 27, 2023 at 9:06 AM David Benjamin
wrote:
> Responses inline.
>
> On Fri, Oct 27, 2023 at 5:04 AM Michael P1 wrote:
>
>> Hi All,
>>
>> Thank you for this interesting draft, I had a couple of quick questions.
>>
>> OpenSSL has been mentioned in this thread, but I was wondering if you
On Tue, Oct 24, 2023 at 10:12:56PM -0400, David Benjamin wrote:
>Additionally I want to emphasize that, because of the negotiation order
>between versions and client certificates, there is no way to do an
>incremental transition here. Saying deployments stick with 1.2 not only
>impa
On Fri, Oct 27, 2023 at 2:07 PM Benjamin Kaduk wrote:
> On Tue, Oct 24, 2023 at 10:12:56PM -0400, David Benjamin wrote:
> >Additionally I want to emphasize that, because of the negotiation
> order
> >between versions and client certificates, there is no way to do an
> >incremental tra
