The following errata report has been verified for RFC8996, "Deprecating TLS 1.0 and TLS 1.1".
-------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7103 -------------------------------------- Status: Verified Type: Editorial Reported by: Martin Thomson <m...@lowentropy.net> Date Reported: 2022-08-24 Verified by: Paul Wouters (IESG) Section: GLOBAL Original Text ------------- <a href="https://www.rfc-editor.org/rfc/rfc%E2%80%8B%204162"; class="eref"> 4162</a> Corrected Text -------------- <a href="https://www.rfc-editor.org/rfc/rfc4162"; class="eref">4162</a> Notes ----- (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. -------------------------------------- RFC8996 (draft-ietf-tls-oldversions-deprecate-12) -------------------------------------- Title : Deprecating TLS 1.0 and TLS 1.1 Publication Date : March 2021 Author(s) : K. Moriarty, S. Farrell Category : BEST CURRENT PRACTICE Source : Transport Layer Security Area : Security Stream : IETF Verifying Party : IESG _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
