The wording issues here are actually a bit tricky. We've done several TLS standards upgrades over time, and there are still a few to go:

Done sometime in the past:

• HTTPS enforcement with 301s
• HSTS lock-on
• SSLv3 removal
• 3DES support removed (and there were a few others like this of less note)
• Forward-secrecy enforcement

Doing now:

• Removing TLSv1.0 and TLSv1.1

Known things coming in the future

• Removing DHE support
• Requiring AEAD ciphers
• Much more distant: removing TLSv1.2 support (sometime long after we've added 1.3!)

So the general language issues around relative levels of security, and more security to come down the line, are still as relevant today as they were back then. The browser/OS version standards and upgrade recommendations are meant to cover at least up through the future DHE and AEAD changes, but obviously enforcing TLSv1.3-only, which is pretty far off in the future and would require even higher minimum version levels. Perhaps we should at least further re-word the parts about IE11 to favor edge more, since IE11 doesn't do 1.2 by default (as noted).

The swap of Traffic for Traffic-Icebox in this ticket's set of tags was based on a bulk action for all such tickets that haven't been updated in 6 months or more. This does not imply any human judgement about the validity or importance of the task, and is simply the first step in a larger task cleanup effort. Further manual triage and/or requests for updates will happen this month for all such tickets. For more detail, have a look at the extended explanation on the main page of Traffic-Icebox . Thank you!