IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Sun, 06 January 2019 01:08 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 C574B130E73 for <uta@ietfa.amsl.com>; Sat, 5 Jan 2019 17:08:33 -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=M2arTsrT; dkim=pass (1536-bit key) header.d=taugh.com header.b=OdlZ9rOp
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 mfGVE0IcWz1c for <uta@ietfa.amsl.com>; Sat, 5 Jan 2019 17:08:31 -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 986A6130DD7 for <uta@ietf.org>; Sat, 5 Jan 2019 17:08:31 -0800 (PST)
Received: (qmail 55524 invoked from network); 6 Jan 2019 01:08:29 -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=d8df.5c31550d.k1901; bh=nqpIAIGCgJS1XXIqb4fZu/Cg+VdQ0q772bD3eDxVb8o=; b=M2arTsrT9Rr0D0cbXzMqv8y1cnItpBTIyiQs/hqQiPG7c9Q6l/leOb3DUB91iThC+616IkBOSlcHjwwtD/IBzcCRHW1378SxDI0gkQMAfc+syZ1byWvkeitWs9ml60JRz1iNrhUebkeOzP1ublGPde0r62lTXHuU/UbW8kTzOyrs/jrW9zfpDms6Ew/v9U3NW8ySX+PkO3h/qOsH0XCDsUxvoqodVWXXPAC5xsBodjDY1oyihLGMQuMBwGaI9nqd
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=d8df.5c31550d.k1901; bh=nqpIAIGCgJS1XXIqb4fZu/Cg+VdQ0q772bD3eDxVb8o=; b=OdlZ9rOpgOIWjF9IoZ+dgtyxDNAxSA3nL5Sa6BfMfNfdTspKgF22GSTVpnMWsSH8XRgUtIecvM0SLVXB3uEAdMyZdNndI417DPs6LGSQTD4dkbVnUMYc4xJw9/bkhJD4fj//JjCLoRrgoP/1MkBjOljR0LItE3sC4qH2UIQzHp5s1ZwCw0f+bgygIqnLGwwzOHjFLVx6LRVBfIkXfXgbJUcIJbSJmCCQQIcenoWlsNveR14mPTgEgigFqFMH+NVs
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 01:08:28 -0000
Received: by ary.qy (Postfix, from userid 501) id CC431200C5ED52; Sat, 5 Jan 2019 20:08:28 -0500 (EST)
Date: Sat, 05 Jan 2019 20:08:28 -0500
Message-Id: <20190106010828.CC431200C5ED52@ary.qy>
From: John Levine <johnl@taugh.com>
To: uta@ietf.org
Cc: giri@dombox.org
In-Reply-To: <CAOEezJTyEf+Sn9ZqQPue1DFUSoFO211YogJ6ufYJxswWzXk=_A@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/IjxoWFVvRF2ADTqaLXWHjxDoliM>
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 01:08:34 -0000

In article <CAOEezJTyEf+Sn9ZqQPue1DFUSoFO211YogJ6ufYJxswWzXk=_A@mail.gmail.com> you write:
>> For one thing, it doesn't work with IDNs.

>I just tested "26pref-español.mydomain.com
><http://xn--26pref-espaol-skb.mydomain.com>" in this page
><https://www.verisign.com/en_US/channel-resources/domain-registry-products/idn/idn-conversion-tool/index.xhtml?loc=en_US>
>
>The output looks like "xn--26pref-espaol-skb.mydomain.com". So instead of
>"if string starts with", we should go for "if string contains".

IDNs use a complex encoding and there is no reason to assume the encoding
won't occasionally include the string "26pref".

Really, this is what SRV is for.  It's not hard to program, and we all
know that mail is not the web and the time for DNS lookups (of which
there are already at least two, more if there's multiple MX) is not in
the critical path.  If you want to be clever, do the SRV and MX
lookups at the same time.

v2.46.0 | Report a Bug | By Email | System Status