Hi! With -rfc8447bis in WGLC, it’s time to get this I-D moving along the
standardization path.
Cheers,
spt
> On Oct 16, 2024, at 22:59, Sean Turner via Datatracker
> wrote:
>
> Sean Turner has requested publication of draft-ietf-tls-rfc8446bis-11 as
> Proposed Standard on behalf of the TLS w
Sean Turner has requested publication of draft-ietf-tls-rfc8446bis-11 as
Proposed Standard on behalf of the TLS working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-tls-rfc8446bis/
___
TLS mailing list -- t
OK. Erik, Mike, Paul: Let me know if you have any further comments on #18.
--Ben
From: Sean Turner
Sent: Wednesday, October 16, 2024 3:06 PM
To: draft-ietf-tls-svcb-ech.auth...@ietf.org
Cc: dn...@ietf.org WG ; TLS List
Subject: Re: [TLS] [DNSOP] Re: Re: Re: Re
This email starts the working group last call for "IANA Registry Updates for
TLS and DTLS” I-D, located here:
I found a few nits. Diff at https://github.com/tlswg/rfc8447bis/pull/58/files
___
TLS mailing list -- tls@ietf.org
To unsubscribe send an ema
Authors (Ben, Mike, and Eric),
Thank for the PR with some examples:
https://github.com/tlswg/draft-ietf-tls-svcb-ech/pull/18
Once you’ve settled the debate (hopefully before Monday), please go ahead and
merge so that Paul can get the IETF LC started.
Cheers,
spot
> On Oct 9, 2024, at 09:38, Se
This email starts the working group last call for "IANA Registry Updates
for TLS and DTLS” I-D, located here:
https://datatracker.ietf.org/doc/draft-ietf-tls-rfc8447bis/
The WG Last Call will end Wednesday October 30th 2024 @ 2359 UTC.
Please review the I-D and submit issues and pull requests vi
On Wed, Oct 16, 2024 at 10:22 AM Paul Wouters wrote:
>
> On Wed, 16 Oct 2024, Martin Thomson wrote:
>
> > A retry fallback happens with the public name. The server that offers ECH
> > lists a public name. If the ECH config (for key A) turns out to be
> > unusable, the server offers a regular h
On Wed, 16 Oct 2024, Martin Thomson wrote:
A retry fallback happens with the public name. The server that offers ECH
lists a public name. If the ECH config (for key A) turns out to be unusable,
the server offers a regular handshake with that public name, where it offers
retry_configs.
So,
