Paul,

I think you can mark this one as verified.  I don’t think anybody is really 
confused by not citing 2446 in the 1st sentence but the quoted sentence is in 
RFC 2446 so as suggested the sentence is still true.

spt

> On Oct 19, 2018, at 23:33, RFC Errata System <rfc-edi...@rfc-editor.org> 
> wrote:
> 
> The following errata report has been submitted for RFC6176,
> "Prohibiting Secure Sockets Layer (SSL) Version 2.0".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata/eid5536
> 
> --------------------------------------
> Type: Editorial
> Reported by: Eugene Adell <eugene.ad...@gmail.com>
> 
> Section: 1
> 
> Original Text
> -------------
>   RFC 4346 [TLS1.1], and later RFC 5246 [TLS1.2], explicitly warned
>   implementers that the "ability to send version 2.0 CLIENT-HELLO
>   messages will be phased out with all due haste".  This document
>   accomplishes this by updating the backward compatibility sections
>   found in TLS [TLS1.0][TLS1.1][TLS1.2].
> 
> Corrected Text
> --------------
>   RFC 2246 [TLS1.0], and later RFC 4346 [TLS1.1], then RFC 5246
>   [TLS1.2] explicitly warned implementers that the "ability to send
>   version 2.0 CLIENT-HELLO messages will be phased out with all due
>   haste". This document accomplishes this by updating the backward
>   compatibility sections found in TLS [TLS1.0][TLS1.1][TLS1.2].
> 
> Notes
> -----
> The warning on the version 2.0 Client Hello is as old as the first TLS 
> version (RFC 2246 Appendix E). That's what the authors meant and wanted to 
> highlight by listing two of the three RFCs containing this warning. This is 
> confirmed by their last sentence. It looks like a small mistake without 
> concrete effects, I push this errata considering "IESG Processing of RFC 
> Errata for the IETF Stream rule 6"
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC6176 (draft-ietf-tls-ssl2-must-not-04)
> --------------------------------------
> Title               : Prohibiting Secure Sockets Layer (SSL) Version 2.0
> Publication Date    : March 2011
> Author(s)           : S. Turner, T. Polk
> Category            : PROPOSED STANDARD
> Source              : Transport Layer Security
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG

_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls

Reply via email to