RFC Errata

Errata Search

Source of RFC  
Summary Table Full Records

RFC 8996, "Deprecating TLS 1.0 and TLS 1.1", March 2021

Source of RFC: tls (sec)
See Also: RFC 8996 w/ inline errata

Errata ID: 7103
Status: Verified
Type: Editorial
Publication Format(s) : TEXT, PDF, HTML

Reported By: Martin Thomson
Date Reported: 2022-08-24
Verifier Name: Paul Wouters
Date Verified: 2024-01-17

Throughout the document, when it says:

<a href="https://www.rfc-editor.org/rfc/rfc%E2%80%8B%204162"
class="eref">​ 4162</a>

It should say:

<a href="https://www.rfc-editor.org/rfc/rfc4162"


(Note: the line wrapping here is mine; the errata tool assumes that this is text, so it won't accept long lines.)

The text for this specification is OK, but the HTML rendering has some hard-to-notice errors in the "Updates" field in the metadata block that is being caused by errors in the XML source.

The XML source includes a number of Unicode zero width space characters (U+200B) after commas in the rfc@updates attribute. xml2rfc is unable to handle these characters correctly, treating them - and the space that follows - as part of the RFC number. It generates the bad link as you see above.

This can be addressed in xml2rfc, maybe, but this is probably not XML we want to permit.

Paul Wouters (AD): Verified, as this RFC won't get any updates.

Report New Errata

Advanced Search