It should, or 'TLS/SSL'. But so many people - even in tech - still use 'SSL' as a synonym for 'PKI on the web' that it's better to be understood than correct (and yes it's a bit sad).

Also: SSLv3 and TLSv1 are very similar: http://tim.dierks.org/2014/05/security-standards-and-name-ch...

When the IETF renames things, everyone is going to have a bad time. See also URI and IRI.

Wow, I've never even heard of IRI.

Guess that proves your point :-D

I think HTTPS has more name recognition than SSL.

Each of the tools involved refer to their the overall https configuration as SSL. Even if it's not the protocol which is being used, it's a reasonable choice for the tool name.

Apache

SSLProtocol all -SSLv2 -SSLv3 -TLSv1

SSLCipherSuite ECDHE-RSA-AES1....

Nginx

ssl_protocols TLSv1.1 TLSv1.2;

ssl_ciphers 'ECDHE-RSA-AES....'

HAProxy

ssl-default-bind-ciphers ECDHE-RSA-....