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

John C Klensin <john-ietf@jck.com> Mon, 07 January 2019 12:41 UTC

Return-Path: <john-ietf@jck.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 56062130E0A for <ietf-smtp@ietfa.amsl.com>; Mon, 7 Jan 2019 04:41:24 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
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 ebuQ0Qu7wWlW for <ietf-smtp@ietfa.amsl.com>; Mon, 7 Jan 2019 04:41:23 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D426D123FFD for <ietf-smtp@ietf.org>; Mon, 7 Jan 2019 04:41:22 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ggUDZ-0006e0-Aj; Mon, 07 Jan 2019 07:41:21 -0500
Date: Mon, 07 Jan 2019 07:41:16 -0500
From: John C Klensin <john-ietf@jck.com>
To: Viruthagiri Thirumavalavan <giri@dombox.org>
cc: ietf-smtp@ietf.org
Message-ID: <D153754716471B0D9A8D8DE9@PSB>
In-Reply-To: <CAOEezJSnPcz919k87fS5RFK5dtVSfqn00ow-QtxudDdm9rP9_w@mail.gmail.com>
References: <CAOEezJQL_2_YUDJ3UW6MJ2pDtBzEwKDMV3a5PAvDqwmg5Gd6Xw@mail.gmail.com> <20190107085807.GA9513@ams-1.poolp.org> <CAOEezJSnPcz919k87fS5RFK5dtVSfqn00ow-QtxudDdm9rP9_w@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/feUeBNFk_3uPGpa2YfEpgW1UDdA>
Subject: Re: [ietf-smtp] SMTP Over TLS on Port 26 - Implicit TLS Proposal
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: Mon, 07 Jan 2019 12:41:24 -0000


--On Monday, January 7, 2019 15:53 +0530 Viruthagiri
Thirumavalavan <giri@dombox.org> wrote:

> Trillions of mails sent every year. Why do we have to waste
> trillion of requests every year in trying for 465 when the
> signalling step can be embedded in the mx host name?
> 
> Can you give me a good reason, not to go for my solution?

Borrowing a bit from the note I sent a few minutes ago (please
read it first), there are efforts all around the world to get
DNS names into local writing systems and compatible with the
writing systems used in local languages -- so-called
"internationalized domain names" or "IDNs"   That effort has
already turned things like 
  www.<label-in-non-latin-script>.<label-in-non-latin-script>
into an ugly mess and invitation to assorted attacks, especially
if that script either looks a lot like Latin or is mostly
written right to left.   Naming conventions have their place and
can be really convenient, but turning them into protocol
elements rather than hints for convenience is just a really bad
idea.

If DNS tricks are needed and useful, use SRV records.

    john