Hi Stephen,
And RFC 7525 (belonging to BCP 195) states in Section 3.1.1:
o Implementations SHOULD NOT negotiate TLS version 1.1
[...]
o Implementations MUST support TLS 1.2 [RFC5246] and MUST prefer to
negotiate TLS version 1.2 over earlier versions of TLS.
That's why I thought RFC 8143 was already requiring not to use TLS 1.1.
SHOULD NOT != MUST NOT though:-) And in any case, an additional
unnecessary update would be no harm in this case, so I figure it's
best to leave it as-is.
Sure.
(Unless I'm missing some reason why that
UPDATE would do damage, in which case, we should chat more.)
No damage at all.
You can leave it as-is.
So, yes, I've added 7525 to the list of UPDATEd stuff in my copy
and made a change of intended status to BCP. (I bet a beer we'll
change that again >1 time:-)
:)
--
Julien ÉLIE
« Si l'art n'a pas de patrie, les artistes en ont une. » (Camille
Saint-Saëns)
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
