Re: [Endymail] Hashes of key as addresses

Viktor Dukhovni <ietf-dane@dukhovni.org> Fri, 05 September 2014 21:25 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: endymail@ietfa.amsl.com
Delivered-To: endymail@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DE771A02E1 for <endymail@ietfa.amsl.com>; Fri, 5 Sep 2014 14:25:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 nCOOCgS0qvGq for <endymail@ietfa.amsl.com>; Fri, 5 Sep 2014 14:25:44 -0700 (PDT)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 868AC1A0305 for <endymail@ietf.org>; Fri, 5 Sep 2014 14:25:38 -0700 (PDT)
Received: by mournblade.imrryr.org (Postfix, from userid 1034) id 00C6D2AB2C5; Fri, 5 Sep 2014 21:25:37 +0000 (UTC)
Date: Fri, 5 Sep 2014 21:25:37 +0000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: endymail@ietf.org
Message-ID: <20140905212537.GY26920@mournblade.imrryr.org>
References: <CAMm+LwimhUi5uZAgm9erYtMJ9-o6+x__344TwKH4-Pa_-mckfg@mail.gmail.com> <20140829091133.GA25723@yeono.kjorling.se> <CAMm+LwhSYm7e4WevDKqewGuOk=O_Zd7dKa1ctfvBzyF3jz4jtg@mail.gmail.com> <20140904132955.GN603@yeono.kjorling.se> <20140905192712.XG2Xmr5N%sdaoden@yandex.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140905192712.XG2Xmr5N%sdaoden@yandex.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/endymail/WUGyINbVTeMqJMI2iI8Q7ai9dGM
Subject: Re: [Endymail] Hashes of key as addresses
X-BeenThere: endymail@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <endymail.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/endymail>, <mailto:endymail-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/endymail/>
List-Post: <mailto:endymail@ietf.org>
List-Help: <mailto:endymail-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/endymail>, <mailto:endymail-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Sep 2014 21:25:45 -0000

On Fri, Sep 05, 2014 at 08:27:12PM +0200, Steffen Nurpmeso wrote:

> I don't know how many messages are sent over SMTP each day, but it
> would be interesting to know how much energy all those useless
> roundtrip packets consume which are necessary to get upgrade
> a SMTP session via STARTTLS, and how many percent of those
> connections could also instantiate a non-existent SMTPS instead,
> not requiring these upgrades.

SMTP is not that latency sensitive.  Because SMTP starts in cleartext,
servers can and do refuse to STARTTLS with clients they are going
to reject due to poor IP reputation.

There are other advantages.  For example, the server learns the
client's EHLO name before TLS, allowing it to base TLS policy (like
requests for the client certificate) on the the client's EHLO name.
And of course clients that fail to interoperably negotiate TLS can
fall back to cleartext.

All told, STARTTLS is a good fit for SMTP, which unlike HTTP is
not nearly as sensitive to latency.

-- 
	Viktor.