Hi Stephen,
This version attempts to make the few changes discussed
at the meeting on Monday. I wrote a script that gave me
a list of 76(!) RFCs this might need to update, and may
of course have mucked that up, so if anyone has a chance
to check if (some of) those make sense, that'd be great.
I believe updating RFC 4642 (TLS with NNTP) is useless because this RFC
has already been updated by RFC 8143.
In RFC 8143:
A.6. Related to Other Obsolete Wording
The first two sentences of the seventh paragraph in Section 2.2.2 of
[RFC4642] are removed. There is no special requirement for NNTP with
regard to TLS Client Hello messages. Section 7.4.1.2 and Appendix E
of [RFC5246] apply.
That is to say, the following sentences in RFC 4642 are no longer relevant:
Servers MUST be able to understand backwards-compatible TLS Client
Hello messages (provided that client_version is TLS 1.0 or later),
and clients MAY use backwards-compatible Client Hello messages.
Neither clients nor servers are required to actually support Client
Hello messages for anything other than TLS 1.0.
That's why I suggest draft-ietf-tls-oldversions-deprecate does not
update RFC 4642. It is no longer useful.
Are you OK with this analysis?
--
Julien ÉLIE
« Le rire est une chose sérieuse avec laquelle il ne faut pas
plaisanter. » (Raymond Devos)
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
