IETF Logo Mail Archive

Re: [ietf-smtp] smtp improvement?

John C Klensin <john-ietf@jck.com> Tue, 15 September 2020 03:27 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 9C2D23A02BD for <ietf-smtp@ietfa.amsl.com>; Mon, 14 Sep 2020 20:27:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] 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 YfsRJLMqY9Mu for <ietf-smtp@ietfa.amsl.com>; Mon, 14 Sep 2020 20:27:09 -0700 (PDT)
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 B2EEF3A02BC for <ietf-smtp@ietf.org>; Mon, 14 Sep 2020 20:27:09 -0700 (PDT)
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 1kI1cX-000CDX-Ud; Mon, 14 Sep 2020 23:27:05 -0400
Date: Mon, 14 Sep 2020 23:26:59 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brandon Long <blong@google.com>
cc: iloveemail2 <iloveemail2@protonmail.com>, ietf-smtp <ietf-smtp@ietf.org>
Message-ID: <79C39D5A5B7759257A411258@PSB>
In-Reply-To: <CABa8R6t3hmuGyP-=+tidqMp23SHmwddH247=7OwuTDs3NJJzyg@mail.gmail.com>
References: <te1SaFZOMSOjDAcEAvL24CF40exooXRe212SQoZQMoBX8BJyFGmg2KYVr5VTPxH3G5G7myxRvAfLZ7Q_Ok3MRVRlH48GHddeOLSgkpWIMKE=@protonmail.com> <FF9469BF7566121BCD4D30D8@PSB> <CABa8R6t3hmuGyP-=+tidqMp23SHmwddH247=7OwuTDs3NJJzyg@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/Zrr1hPjiDXX0-zBflZOIXfqdaAg>
Subject: Re: [ietf-smtp] smtp improvement?
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: Tue, 15 Sep 2020 03:27:11 -0000


--On Monday, September 14, 2020 17:38 -0700 Brandon Long
<blong@google.com> wrote:

> Yes, I should point out that at Google, we do multiplex
> multiple connections between a proxy frontend and our actual
> smtp servers, but we don't do it at the command level, but at
> the stream level, which is a much simpler mechanism for
> integration and utility across different protocols (we do this
> with imap, pop, xmpp, and probably others, on top of the
> various types of HTTP).
>...

I would be mildly astonished if you were doing anything else.
It raises some questions that I periodically worry about but
none of them are specific to SMTP or even email more generally.

best,
   john

v2.23.0 | Report a Bug | By Email