IETF Logo Mail Archive

Re: [ietf-smtp] MTA-MTA SMTP and TLS-on-connect

John Levine <johnl@taugh.com> Sun, 26 April 2020 22:20 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41D4F3A1450 for <ietf-smtp@ietfa.amsl.com>; Sun, 26 Apr 2020 15:20:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=RTK0B1OM; dkim=pass (1536-bit key) header.d=taugh.com header.b=AC1NyEeQ
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 Ux-Ja66S0P_X for <ietf-smtp@ietfa.amsl.com>; Sun, 26 Apr 2020 15:20:49 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 849603A144E for <ietf-smtp@ietf.org>; Sun, 26 Apr 2020 15:20:49 -0700 (PDT)
Received: (qmail 16851 invoked from network); 26 Apr 2020 22:20:48 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=41cb.5ea60940.k2004; bh=Q1ynKyfA5xe9TvY1vudW6OGXoo1ysoettpvKBA97TQ8=; b=RTK0B1OMRRUhG7XsqHhfVTb4j0Z14Q84q9qH9ZAA5p7LWB+Le5FclAfWE0QPhUusDe8h5PJYZt9bVDCRRDuiC1eSz8PjPAzrhOVs6y2pZsu5/DrsJyevNqn0trDXrqN7uLXbH9yHhQSWB3o4jxCuAfhSi+SOr/T1ZD4i1A2WxVPtrQ2biB1npHuXsC2R43H71Ibx1O8Aq2WGSvZHtYZQUhEwaajF2OYpYTlJXnEx7zLtIGNYc2s8KkQI2Qgcjpz4
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=41cb.5ea60940.k2004; bh=Q1ynKyfA5xe9TvY1vudW6OGXoo1ysoettpvKBA97TQ8=; b=AC1NyEeQPwCZk7ujlfFEDawgkob8yVjTNebMrfxqHOgVlxKsBsaZ6So9pwTgl8XE2fKNCvrtwj2PVo//io1Kb2OLJ05Z+YnIpmr09psVPCA4II48F4WGjUJlmWAK5QUlyDX581BVSeagj/bc5r+pZQ64hP0P06h3y0bE19Pe8lpC/5076n6Etjt0KTV0CtBHMpGSKwC6R6x4ElUhezXaNrj6/jnWM1WAZb/vUfOw21DzdLe0I1zWYGSNXd8unlBP
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 26 Apr 2020 22:20:48 -0000
Received: by ary.qy (Postfix, from userid 501) id DD30A1864B62; Sun, 26 Apr 2020 18:20:58 -0400 (EDT)
Date: Sun, 26 Apr 2020 18:20:58 -0400
Message-Id: <20200426222058.DD30A1864B62@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: jgh@wizmail.org
In-Reply-To: <8d3d7446-db7d-ac04-2a36-258643254630@wizmail.org>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/fisQHR3WD2BUYwrYIp0QaWIf9Is>
Subject: Re: [ietf-smtp] MTA-MTA SMTP and TLS-on-connect
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Apr 2020 22:20:51 -0000

In article <8d3d7446-db7d-ac04-2a36-258643254630@wizmail.org> you write:
>Hi,
>
>Noting that https://tools.ietf.org/html/draft-sheffer-uta-rfc7525bis-00
>section 3.2 says that TLS-on-connect SHOULD be preferred over STARTTLS
>(my rephrasing) - and that while T-o-c is reasonably common for MSA-MTA
>but not for MTA-MTA -
>
>should we think about technical means to facilitate the latter?

Turns out the STARTTLS language was in RFC 7525 and we missed it.

If this draft goes anywhere, I think we should tell them to fix it and
say that STARTTLS and TLS-on-connect are equivalent if the path with
STARTTLS requires its use, which I think reflects reality.

R's,
John

v2.23.0 | Report a Bug | By Email