IETF Logo Mail Archive

Re: [ietf-smtp] ALPN

Claus Assmann <ietf-smtp@esmtp.org> Thu, 29 July 2021 07:02 UTC

Return-Path: <ietf-smtp@esmtp.org>
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 E40F83A14F1 for <ietf-smtp@ietfa.amsl.com>; Thu, 29 Jul 2021 00:02:34 -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 tZoqDdg-oWdE for <ietf-smtp@ietfa.amsl.com>; Thu, 29 Jul 2021 00:02:33 -0700 (PDT)
Received: from kiel.esmtp.org (kiel.esmtp.org [195.244.235.220]) (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 D66B93A14F0 for <ietf-smtp@ietf.org>; Thu, 29 Jul 2021 00:02:32 -0700 (PDT)
Received: from kiel.esmtp.org (localhost. [127.0.0.1]) by kiel.esmtp.org (MeTA1-1.1.Alpha16.0) with ESMTPS (TLS=TLSv1.2, cipher=ECDHE-RSA-AES256-GCM-SHA384, bits=256, verify=OK) id S00000000000659BE00; Thu, 29 Jul 2021 09:02:30 +0200
Received: (from ca@localhost) by kiel.esmtp.org (8.16.0.41/8.12.10.Beta0/Submit) id 16T72UM5089231 for ietf-smtp@ietf.org; Thu, 29 Jul 2021 09:02:30 +0200 (CEST)
Date: Thu, 29 Jul 2021 09:02:30 +0200
From: Claus Assmann <ietf-smtp@esmtp.org>
To: ietf-smtp@ietf.org
Message-ID: <20210729070230.GA30507@kiel.esmtp.org>
Reply-To: ietf-smtp@ietf.org
Mail-Followup-To: ietf-smtp@ietf.org
References: <20210728172631.GA24560@kiel.esmtp.org> <20210729030741.0BDDB2548012@ary.qy> <20210729044632.GA80094@kiel.esmtp.org> <1e72f0b6-d71a-484b-a571-53564bf6a16b@gulbrandsen.priv.no>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <1e72f0b6-d71a-484b-a571-53564bf6a16b@gulbrandsen.priv.no>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/YYtgrEIo5MB3JB7f1-S8Ty-kREg>
Subject: Re: [ietf-smtp] ALPN
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: Thu, 29 Jul 2021 07:02:35 -0000

On Thu, Jul 29, 2021, Arnt Gulbrandsen wrote:

> In this case, we're talking about whether there is one different ALPN or
> four. Either case suffices to protect email servers from being involved in

Since there are already IDs for IMAP and POP3, it seems we are down to
3 (+SMTP) or 4 (+SUBMIT) unless we want to break existing applications?

> I like having one ALPN identifier rather than four, since it requires a
> smaller change to email clients that share/reuse code for using TLS within
> different protocols,

In my code it's just some "context" that is passed to the proper
functions. The "main" problem is to select the right context, esp.
if things are highly configurable (some people might want to run
smtps on a different port).

-- 
Address is valid for this mailing list only, please do not reply
to it direcly, but to the list.

v2.23.0 | Report a Bug | By Email