IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Tue, 08 January 2019 17:26 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 93C79130F13 for <uta@ietfa.amsl.com>; Tue, 8 Jan 2019 09:26:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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=i40cY7aO; dkim=pass (1536-bit key) header.d=taugh.com header.b=XtBRbpHw
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 QbLkDXn5JWLE for <uta@ietfa.amsl.com>; Tue, 8 Jan 2019 09:26:32 -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 90ECD130F11 for <uta@ietf.org>; Tue, 8 Jan 2019 09:26:32 -0800 (PST)
Received: (qmail 34137 invoked from network); 8 Jan 2019 17:26:31 -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=8556.5c34dd47.k1901; bh=TFZxC22BBkwRQTd8SrQxaFpm4oSWSfWBTyUk9MHDmso=; b=i40cY7aO6Vejkt5JnO4CpOjlIAZGg0yYy0XsBmlh9EQjOHZHhekyaw59FovbwVjVrxWuwMF1NPQomF2TGbVZLj3ZIqvvPd5VMdtrHT0WQwrcCyKxKN9xo4HxDSHOLT6YbUiRL/i4cBfwqoktW0b7ih82lVLk/8TwqqGKLZQKmsRgzTwcYMKlyjNlkRMEpSRNCUZ+Q4Z1ijavKgoQvi5wuFL5lqGBVF3myndX45VXG1e2rob5SSSrORaR8zUabUXx
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=8556.5c34dd47.k1901; bh=TFZxC22BBkwRQTd8SrQxaFpm4oSWSfWBTyUk9MHDmso=; b=XtBRbpHweE2cBd6nvWXQZzWFCDbUdkwlND3y+Tl0uZTMtjAp9Bijf8SU3tiEMeEx1NcgBioSixvEToe+jrMSGgPtcuOReQ/3s9GVKPODc2SaMn2SMLGmIos6rx6HRj4bt6+xHpS3QvQ/G83PnkL6gEd4Agk3+mydShVOpcUTS3BQsTkFI4asJ4NHmZuzYzuRQyjdu5pAIZDf4FMICjJcGmhDO6Yg118hFYP2ZcEo/Ne6oinvKQDJxpSAlvbeRBIv
Received: from ary.local ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 08 Jan 2019 17:26:30 -0000
Received: by ary.local (Postfix, from userid 501) id 84DA9200C72467; Tue, 8 Jan 2019 12:26:30 -0500 (EST)
Date: 8 Jan 2019 12:26:30 -0500
Message-Id: <20190108172630.84DA9200C72467@ary.local>
From: "John Levine" <johnl@taugh.com>
To: uta@ietf.org
Cc: dkg@fifthhorseman.net
In-Reply-To: <87k1jfi2dd.fsf@fifthhorseman.net>
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/XVHBasNzVBTKbFE2EcLmI9fK324>
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: Tue, 08 Jan 2019 17:26:35 -0000

In article <87k1jfi2dd.fsf@fifthhorseman.net> you write:
>I think the community would welcome that, but figuring out what specific
>timeline is plausible; getting affirmative buy-in; setting up adequate
>testing and notice; etc, is the real work involved.  It won't happen
>just by wishing it.

MTA-STS does a great deal of this.  It has a way for a domain to say
"all my inbound mail uses TLS" (RFC 8461) and for other systems to
report back and say whether they're actually seeing that (RFC 8460.)

I don't understand why people are trying to reinvent the wheel when we
just defined a fairly round one a few months ago.

-- 
Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly

v2.2.1 | Report a Bug | By Email