IETF Logo Mail Archive

[TLS] Recommending ALPN (was Re: [dns-privacy] Martin Duke's No Objection on draft-ietf-dprive-xfr-over-tls-11 ...)

Martin Thomson <mt@lowentropy.net> Fri, 30 April 2021 00:06 UTC

Return-Path: <mt@lowentropy.net>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6614C3A18FF; Thu, 29 Apr 2021 17:06:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level:
X-Spam-Status: No, score=-2.119 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_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=OvNx3fMY; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ovfZr3UN
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 tYjx3EXUGk8I; Thu, 29 Apr 2021 17:06:12 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0D733A18FD; Thu, 29 Apr 2021 17:06:11 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 10F4B5C00BA; Thu, 29 Apr 2021 20:06:08 -0400 (EDT)
Received: from imap10 ([10.202.2.60]) by compute1.internal (MEProxy); Thu, 29 Apr 2021 20:06:08 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type; s=fm2; bh=WrGL0SPjnG3+/1yRnmKwA+/Fy2dE wK7z7FzUxA3FRkA=; b=OvNx3fMYEju3Ab6+QlXtbJXuwzxqs+MCi5h1hjjgA1Mo HranuhOKttR9/r/HflwFb/1LbG5voH9x9Wtyx61fF3BqCITYPDV69Zqw8diOdRrt CUROZ1l8AQrcUZn5K3nFBxXVSfJbKUaC/NbuUwus1jjtVX9/eSPkYY8y2a9vlCa/ fvEXknHmdmBMQvBon8wdht3yUCGbeigom1Nt1rFS2JfQseLlUc5WuNfxUwEldJa3 2K/PO+xV6d3epQRNLqSvKjEhlCrjUmNXwhptbiZ5+LgGsqm3vP1RGHWaJUb8Mrsp O3znwAjVRqefQd9Wh02hN0hjcFWtIxpJMlOrdi6GWw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=WrGL0S PjnG3+/1yRnmKwA+/Fy2dEwK7z7FzUxA3FRkA=; b=ovfZr3UNMujoSIHOEYjra4 HsK385EeKGS47rDSS7U2iC9UeM18H7QEy9lPPhA3j6ZTfxPSjjk5wqnmefJ9FqH2 naDuK/Kqya7p19yyt3GTS9m1PiG3rZ1W198/DdoKmpAlDjiI/psIWSxF/8NS9Srt cfx/LmA7RP3HPPhAUoO4MQrEgooeD4Kur1fzEMjFcap65xgPIsZ21NPFm5nw7sP/ qk8TD9ecpyxpw3KIrWI+/UQRO3TomARYKLNneHybZUjd06DT5HVOd5CxqCaT/Fz6 hx9W9K9yI/O6b+N0oEhzI/I68Ac9e/+O7Xz1qXL3iw3i2spTZhp1fwEHWelsbvJg ==
X-ME-Sender: <xms:70mLYDJd823QF7VXAOxnGaMwXqfoSgxIzZVmyeU9LlHt1rxplh5ymw> <xme:70mLYHK2ZwT-YaSU4g6XdDU1mW1QSKt-HfLtkIeMOA40qFK4Jgiq1Aae4uOf3AXLz W-AUcZhy0iYVUBu6ho>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvddvhedgfedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreerjeenucfhrhhomhepfdforghr thhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghnthhrohhphidrnhgvtheqnecugg ftrfgrthhtvghrnhepheefteduudduhedtkefhvdfhteelffdujeegjeffheffveekudei gfeuveekfeelnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:70mLYLtyixIB4AqAQxhNnS-Zp82pxtX-hfLiyUxgdnagmfGCG7CbCg> <xmx:70mLYMZHu2FIjAxt2-S_ZDNXnNxPdM7V8v_IWO7Df2sv-0986Os61g> <xmx:70mLYKY3BfoM5D8KMYPKvUWOUkPH7xhTti9jROw6RaQuZibJM-9iXg> <xmx:8EmLYNxFrV_k2bYgviADOZyeSadsM2js9KmolnEL8kPTBBflaLJoQw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 50A9F4E00AB; Thu, 29 Apr 2021 20:06:07 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-403-gbc3c488b23-fm-20210419.005-gbc3c488b
Mime-Version: 1.0
Message-Id: <fe80ee08-eebc-45cf-8d83-51f2da83cb96@www.fastmail.com>
In-Reply-To: <753E5DAA-37C6-4F82-829D-29DA5458C1DB@akamai.com>
References: <161921129877.20343.10624609154750488813@ietfa.amsl.com> <034F6C49-0195-4FAF-9EF2-1E39E809F902@sinodun.com> <7d8fa1d2-ef1a-4ed3-b660-955248a4ec63@www.fastmail.com> <753E5DAA-37C6-4F82-829D-29DA5458C1DB@akamai.com>
Date: Fri, 30 Apr 2021 10:05:48 +1000
From: Martin Thomson <mt@lowentropy.net>
To: "Salz, Rich" <rsalz@akamai.com>
Cc: "tls@ietf.org" <tls@ietf.org>, uta@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/wZoHJkMPmGMnW0-p7w5qHNFNVww>
Subject: [TLS] Recommending ALPN (was Re: [dns-privacy] Martin Duke's No Objection on draft-ietf-dprive-xfr-over-tls-11 ...)
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Apr 2021 00:06:18 -0000

(dprive to bcc, because this is getting further afield)

On Fri, Apr 30, 2021, at 00:26, Salz, Rich wrote:
> >    No new protocol should use TLS without ALPN.  It only opens space for cross-protocol attacks.  Did the working group consider this possibility in their discussions?
> 
> I don't believe that message has been made as public as it should be.

I see that UTA is working on a revision of RFC 7525.  Is text on this something that would be in scope.  I only just searched for "ALPN", finding nothing, so maybe it is not in the original scope and maybe there are things that might prevent expansion of scope.

v2.23.0 | Report a Bug | By Email