Re: [Tls-reg-review] TLS ALPN registry: request to add SMTP
Simon Ser <contact@emersion.fr> Fri, 01 December 2023 14:08 UTC
Return-Path: <contact@emersion.fr>
X-Original-To: tls-reg-review@ietfa.amsl.com
Delivered-To: tls-reg-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3A12C15108F for <tls-reg-review@ietfa.amsl.com>; Fri, 1 Dec 2023 06:08:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=emersion.fr
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id twj7eWJdKJQF for <tls-reg-review@ietfa.amsl.com>; Fri, 1 Dec 2023 06:08:19 -0800 (PST)
Received: from mail-4317.proton.ch (mail-4317.proton.ch [185.70.43.17]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 326D6C151089 for <tls-reg-review@ietf.org>; Fri, 1 Dec 2023 06:08:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=emersion.fr; s=protonmail2; t=1701439694; x=1701698894; bh=cweuqnh99lKIHg2z1VX6kuDQvAPeYkmT1Wa4yzwq+KE=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=Bxq5gOiZYqbO2w8n27RDMhDtrUxgy7K3rSVa07ArvTaJRLHWY0AS2FZr1qvPVt+6h u1V2yPc9MbWr72pKbb1XIEGSCb8oVIvhuyjKdP1u3CjAE9TrWflxlXdJqfBhb2g2X8 mynfu51k8c3gCW/RudraahdwJ72UxDnALdr0bT+Ty6W2qEIJLz2GAUlUt46NDllkRh eoHrfxkE57wsosZg2EK4kPiPDUi84nGvsu1xu2q5tIQpSiTmCYKa1D3nLYg1reC8SQ RnUTBTPyZpuOUyomKQ3KBVb9MwpF/bDq1nTRbuVFt69+FoDhdFLTeJQXMYzFiv14lu 3hnoXWxKbeMTQ==
Date: Fri, 01 Dec 2023 14:07:00 +0000
To: "Salz, Rich" <rsalz@akamai.com>
From: Simon Ser <contact@emersion.fr>
Cc: "tls-reg-review@ietf.org" <tls-reg-review@ietf.org>
Message-ID: <rAdN2sfFWsEUmzwJKrixdIfAe_8jz_TBjvNfLhiF89XHy50iUQVccVo2LdVVLAxPo72OvMBIGmlNMSnz0PD_VfvvnEnGzj3QN79cHVdVJJU=@emersion.fr>
In-Reply-To: <50B0AE6A-7037-4D35-98B4-53E0D7890465@akamai.com>
References: <RECmtoQB48mRB8wGTCO91YuonGAoQ4kmzutPdhz8nbmD-oKYGiFrmNImTwdgCoMoiNYs5OPt1W3szOq-gGlYb16hmYaeVmfx1gYlIp4lR-4=@emersion.fr> <50B0AE6A-7037-4D35-98B4-53E0D7890465@akamai.com>
Feedback-ID: 1358184:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/iw4Ht2-abpeiothTOzx98nGkR4c>
Subject: Re: [Tls-reg-review] TLS ALPN registry: request to add SMTP
X-BeenThere: tls-reg-review@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: TLS REVIEW <tls-reg-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls-reg-review>, <mailto:tls-reg-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls-reg-review/>
List-Post: <mailto:tls-reg-review@ietf.org>
List-Help: <mailto:tls-reg-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls-reg-review>, <mailto:tls-reg-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Dec 2023 14:08:24 -0000
On Friday, December 1st, 2023 at 14:53, Salz, Rich <rsalz@akamai.com> wrote: > 1. That RFC does not mention TLS. Right. Maybe 8314 section 3.3 is a better reference. > 4. So are you proposing port 443 for SMTP/TLS? Do POP and IMAP get > involved? Yeah. IMAP already has an ALPN identifier. > 5. Have you had dicussions with other people in the email community > about this? Perhaps the IETF mail extensions working group is a good > place to start, https://datatracker.ietf.org/wg/mailext/about/ Okay. I'll keep this on my TODO list, but not sure when I'll have time to do this.