IETF Logo Mail Archive

Re: IETF mail server and SSLv3

Jari Arkko <jari.arkko@piuha.net> Tue, 26 January 2016 21:16 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DC6E1B3169 for <ietf@ietfa.amsl.com>; Tue, 26 Jan 2016 13:16:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cffiqQtTcqJF for <ietf@ietfa.amsl.com>; Tue, 26 Jan 2016 13:16:06 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 9A4641B3168 for <ietf@ietf.org>; Tue, 26 Jan 2016 13:16:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id DC5BF2CC9A; Tue, 26 Jan 2016 23:16:03 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id esp_TDZ-3l3s; Tue, 26 Jan 2016 23:16:03 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 56B102CC6C; Tue, 26 Jan 2016 23:16:03 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Subject: Re: IETF mail server and SSLv3
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_ABEDEC2D-96C9-4A66-98C0-75FC5E6DA7BD"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail 2.5.2
From: Jari Arkko <jari.arkko@piuha.net>
X-Priority: 3
In-Reply-To: <000a01d1585b$60b68e60$4001a8c0@gateway.2wire.net>
Date: Tue, 26 Jan 2016 23:16:00 +0200
Message-Id: <FD83B269-D641-4207-B4EE-922747449B2E@piuha.net>
References: <F38A9FEF-7DBB-4F40-860E-6CB425E5EEE3@ietf.org> <000a01d1585b$60b68e60$4001a8c0@gateway.2wire.net>
To: "tom p." <daedulus@btconnect.com>, Phillip Hallam-Baker <phill@hallambaker.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/V0X0AZ-4UONP7dEqBq0ImTQElTo>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jan 2016 21:16:08 -0000

Tom, Phillip,

Impressive? Not much. If anything, I feel a bit
embarrassed that we are updating our servers
only now :-)

This really was just an IETF service announcement.
The tools team felt that if we are making changes
we should announce them rather than surprise
anybody. We plan to announce similar other things
as well, when there are changes. And I certainly
believe this particular change was a technically
reasonable thing to do.

We do of course have other things to discuss —
how much the IETF is doing for improving email
security in the Internet, and what can be done to
it to begin with. But that is a broader topic that
IMO, doesn’t have much to do with what specific
arrangements we have for our own e-mail
server (and at a particular layer of that server,
even).  Phillip’s questions are very rasonable
in that broader topic, however.

Jari

v2.23.0 | Report a Bug | By Email