Hi! There is consensus to adopt this draft as a working group item.* This might
not be the exact form it ends up in, but there is sufficient interest to get
the work started. I'll work with the authors to migrate to the official
repository and submit an updated draft.
spt
* Apologies for takin
I support adoption.
Thanks,
Aritra.
___
TLS mailing list -- tls@ietf.org
To unsubscribe send an email to tls-le...@ietf.org
Hi Sean,
At 09:39 AM 25-07-2024, Sean Turner wrote:
At the IETF 120 TLS session there was interest in adopting the
Extended Key Update for TLS 1.3 I-D
(https://datatracker.ietf.org/doc/draft-tschofenig-tls-extended-key-update/).
This message starts a two-week call for adoption. If you support
I also support adoption of this draft.
I share David's observation that the client and server could simultaneously
initiate an Extended Key Update, but I had a different mitigation in mind: each
side chooses a random value and the higher value wins if there is another
ExtendedKeyUpdate alread
I support adoption of the draft to solve this problem, but I suspect the
construction will need some changes. I'm not sure the construction in the
draft actually works.
A single extended key update flow in the draft sends NewKeyUpdate in
*both* directions.
Now, imagine if both client and server in
> On 25. Jul 2024, at 09:39, Sean Turner wrote:
>
> At the IETF 120 TLS session there was interest in adopting the Extended Key
> Update for TLS 1.3 I-D
> (https://datatracker.ietf.org/doc/draft-tschofenig-tls-extended-key-update/).
> This message starts a two-week call for adoption. If you su
The FATT-related slides that were presented yesterday said:
~~~
Mechanism: triage, then maybe analyze
At document/change adoption call, chairs email the triage panel, bring
summarized analysis to the WG as part of the adoption discussion.
~~~
I now realize that this is ambiguous. At what point
company-registration-information.html>
for Company Registration
From: Bob Beck
Sent: Thursday, July 25, 2024 1:35 PM
To: Sean Turner
Cc: TLS List
Subject: [TLS]Re: Adoption call for Extended Key Update for TLS 1.3
I support adoption, and would be willing to review drafts and would work to
I support adoption.
On Thu, 25 Jul 2024 at 10:37, Bob Beck
wrote:
> I support adoption, and would be willing to review drafts and would work
> to have it implemented.
>
> On Thu, Jul 25, 2024 at 9:44 AM Sean Turner wrote:
>
>> At the IETF 120 TLS session there was interest in adopting the Exten
I support adoption, and would be willing to review drafts and would work to
have it implemented.
On Thu, Jul 25, 2024 at 9:44 AM Sean Turner wrote:
> At the IETF 120 TLS session there was interest in adopting the Extended
> Key Update for TLS 1.3 I-D (
> https://datatracker.ietf.org/doc/draft-ts
I support adoption. I will review the drafts and work to get it implemented
___
TLS mailing list -- tls@ietf.org
To unsubscribe send an email to tls-le...@ietf.org
11 matches
Mail list logo
