---- Original Message -----
From: "IETF Chair" <chair(_at_)ietf(_dot_)org>
To: "IETF Announcement List" <ietf-announce(_at_)ietf(_dot_)org>
Cc: "IETF" <ietf(_at_)ietf(_dot_)org>
Sent: Monday, January 25, 2016 7:39 PM
For your information, while SSLv3 has been disabled on IETF web servers,
it has still been enabled on mail transport. The tools is taking action
to disable SSLv3 even on mail transport. After this, all IETF web and
mail servers support only TLS-based transport on secure connections.
If you have any feedback regarding this, let me or the tools team know.
<tp>
It seems a somewhat strange executive decision. e-mail, famously, is
not end-to-end so what happens between the IETF mail servers and
whatever E/ISP the IETF uses seems like a local decision that does not
affect the service I get (whereas what happens between my e-mail client
and the E/ISP that I use has a major impact on the service I get).
So this looks like an impressive sounding announcement in advancing the
field of privacy that actually does not mean very much.
Tom Petch
Jari Arkko, IETF Chair