>There are three references to [RFC8446] that should be updated. [RFC8446]
should be removed from the reference section.

Fixed

> The info for [RFC8446bis] in the reference section is wrong. It is just
copy pasted from [RFC8446]

Trying to do !RFC8446bis just picked up the old 8446 info, fixed

> Some browsers do not let me access the URL as I have not installed the
DoD Root Certificate. When using Firefox, I get a CNSS.gov Error Message
instead of the document

We weren't even using that ref anymore, removed, along with eight other now
dead references

> [DOWLING]

> The URL should be https://doi.org/10.1007/s00145-021-09384-1

Fixed

> [tlsiana]

> This should point to RFC 9847 instead of draft-ietf-tls-rfc8447bis

Fixed

> OLD: John Mattsson
> NEW: John Preuß Mattsson

Fixed

https://github.com/tlswg/draft-ietf-tls-mlkem/blob/main/draft-ietf-tls-mlkem.md?plain=1

The Editor's Copy job keeps saying it's running but it's not rendering
these updates...

On Wed, Jun 24, 2026 at 11:44 AM John Mattsson <[email protected]>
wrote:

> All my issues have been addressed. I support publication.
>
>
> Some Editorial comments:
>
> ----
>
> Russ Housley wrote
> >Section 4.2: s/[RFC8446]/[RFC8446bis]/
>
> There are three references to [RFC8446] that should be updated. [RFC8446]
> should be removed from the reference section.
>
> The info for [RFC8446bis] in the reference section is wrong. It is just
> copy pasted from [RFC8446]
>
> ----
>
> [CNSSP15]
>
> Some browsers do not let me access the URL as I have not installed the DoD
> Root Certificate. When using Firefox, I get a CNSS.gov Error Message
> instead of the document.
>
> ---
>
> [DOWLING]
>
> The URL should be https://doi.org/10.1007/s00145-021-09384-1
>
> ---
>
> [tlsiana]
>
> This should point to RFC 9847 instead of draft-ietf-tls-rfc8447bis
>
> ---
>
> OLD: John Mattsson
> NEW: John Preuß Mattsson
> (My emails are lying)
>
> ---
>
> Cheers,
> John Preuß Mattsson
>
>
_______________________________________________
TLS mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to