IETF Logo Mail Archive

Re: [Uta] SMTP Over TLS on Port 26 - Implicit TLS Proposal

"John Levine" <johnl@taugh.com> Sun, 06 January 2019 03:59 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: uta@ietfa.amsl.com
Delivered-To: uta@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89238130FB5 for <uta@ietfa.amsl.com>; Sat, 5 Jan 2019 19:59:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-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=2HATTys6; dkim=pass (1536-bit key) header.d=taugh.com header.b=vosXvUFd
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 ybcWiZ5s9j0U for <uta@ietfa.amsl.com>; Sat, 5 Jan 2019 19:59:10 -0800 (PST)
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 671D3130F63 for <uta@ietf.org>; Sat, 5 Jan 2019 19:59:10 -0800 (PST)
Received: (qmail 87888 invoked from network); 6 Jan 2019 03:59:07 -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=1574d.5c317d0b.k1901; bh=iCV9vEZT3acBTdcPF+RQ3c1IXjgxJ9/UMXduCCk2AP0=; b=2HATTys6HgEXRItMd7e97qtttVHyWBukdyR1WqDL5t5j9Fbey61o44yV1TG2hNcLdd2l3ZrM/+Yy+UH+aybhPEiGQYhCKzYGXEggiVxeQBnCTN6BRnZZsEBmvJ+gOcmDW12BjYRSjgSVqZkTxC03p2DIdNYePJAywF5BNI7xtoUyxg5BOEjhwM5Xm9xfRCDvaHAtxAsEh7/4Nx2g08xyZFH1cTtuxWQYkcMFums0nrno/Uf7VKPU/aCwIml/bLKB
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=1574d.5c317d0b.k1901; bh=iCV9vEZT3acBTdcPF+RQ3c1IXjgxJ9/UMXduCCk2AP0=; b=vosXvUFdHQEHTNOxkeRzh7bXkyHlw5QteL8fBL9NzeZXQL25e0O94PRcs3PVhgHZ7PEzV0ygJ7Dztl/ALyWhfa1iUUyMDCApI9QbEW0DlfY+dy0xFsOt7A2RjPYy6CHFWZFILTOT3Do+lf2MYypIj9gIYIToDPEv9AGzPS+JT/6ZJf7zFc7ySU7azA6Q0pUpgPSmdfAvbNo5fL9QF9qH6J4jHZaUBX/iF/LtBx99zj0HyMoPnvzbM8JqxPRi7MhO
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; 06 Jan 2019 03:59:07 -0000
Received: by ary.qy (Postfix, from userid 501) id 1E402200C60734; Sat, 5 Jan 2019 22:59:06 -0500 (EST)
Date: 5 Jan 2019 22:59:06 -0500
Message-Id: <20190106035907.1E402200C60734@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: uta@ietf.org
Cc: giri@dombox.org
In-Reply-To: <CAOEezJTb_=+utH8=cT8_6UFfkq7E4-qKUOZh5donPQKZwmePnw@mail.gmail.com>
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/uta/CaMj7xkGpkDg6c3qKGlLjksG5do>
Subject: Re: [Uta] SMTP Over TLS on Port 26 - Implicit TLS Proposal
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: UTA working group mailing list <uta.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uta>, <mailto:uta-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uta/>
List-Post: <mailto:uta@ietf.org>
List-Help: <mailto:uta-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uta>, <mailto:uta-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jan 2019 03:59:13 -0000

In article <CAOEezJTb_=+utH8=cT8_6UFfkq7E4-qKUOZh5donPQKZwmePnw@mail.gmail.com> you write:
>> I stand by the "has no merit" assessment.  Nobody is going to turn
>> off port 25 support overnight.
>
>I presume you didn't read my document. It's all about turn off port 25 ten
>years from the standard publication date. Not overnight.

Sorry, but this is a fantasy.  SMTP routing still falls back to an A
record if there's no MX and the DNS has been around for 30 years.  And
your assmptions about what is hard and what is easy may be correct for
your personal situation, but they are not true in general.

Look at it this way -- if you can set up an STS server in less than a
decade, you're ahead of the game.

R's,
John

v2.2.1 | Report a Bug | By Email