Re: [TLS] Consensus call on codepoint strategy for draft-ietf-tls-hybrid-design

Christopher Wood <caw@heapingbits.net> Mon, 01 May 2023 09:59 UTC

Return-Path: <caw@heapingbits.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 E7E34C1522B9 for <tls@ietfa.amsl.com>; Mon, 1 May 2023 02:59:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 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_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, 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=heapingbits.net header.b="HAhcZgjb"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="kubrKVOf"
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 LzCBaYiEHkJb for <tls@ietfa.amsl.com>; Mon, 1 May 2023 02:59:11 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 8D887C15199D for <tls@ietf.org>; Mon, 1 May 2023 02:59:11 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id A745E5C00F8 for <tls@ietf.org>; Mon, 1 May 2023 05:59:10 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Mon, 01 May 2023 05:59:10 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heapingbits.net; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1682935150; x=1683021550; bh=s56sCmFSEgzUfMAnCby4EOtJBZ8kFybo2ZR Wj8B+QDA=; b=HAhcZgjbmhuNsDNuFRhXXEtvXxhB8Y2jBAwEnCMcVBdHKM78Fy6 Efy43ItEZmZWD+vgCX+sgAQDXGQ6piNCMRcGBHc03domzM6Mdfn0I4veGiLM+xEN NQEtLadt1whTUDlyMwQIvTa3U4/gRvKnZprQFS1Jp1UBq7goJT1e4im0aI5qWATv ZdIIwYsbBcAW5O7pgTnphVhbkI7wgZXP1GCbd7PTRy2QhwJaBwLkPxJXVTeAucKy I1hxRlPH3WmBW/mZThi7gsFECmUO9FY3uf40KyHjSOMlVWEMMdUg9d17VllIf1Oo 0FksdMAyZUk49/TrSwAgwpRU3Dp9M3lI5uQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1682935150; x= 1683021550; bh=s56sCmFSEgzUfMAnCby4EOtJBZ8kFybo2ZRWj8B+QDA=; b=k ubrKVOfwP5jiUPpezcS7f4geyjSZK4Z6TScYMRqfW3XDjF7aD+jLwu5aibw7J8l4 ndq8udPVELfOpOexJgWiHZk+LSjjv/FrKSebYH0W7NEFFm//ZSXYhNxZBN58XaUF K1/A5dF9IqJUumeqrd7I69/cdDs5J7/maD7B2JuF8oRJU9P4mpVK1vvAs6bHTMfJ /sCI7kEeIZRcjhVDYXe09BycmG/JCEmda8YXLQho298sWt0wb6OTJYLk1sbLO0uX Xuqq0Z7QwIjy5nUU5L+Xc7gHmiBu/NnbyvgrjbcmzVFnFYz3BvE5O+ddJbYkLRK1 M/s+XK9O8x10RHUBI8nkA==
X-ME-Sender: <xms:bo1PZJVNWGDslMss8EIvdsTck4XWtybuhgV5OGinxtdxJ03pe9vqAA> <xme:bo1PZJkCn16gNMN5C-a5Et8paNrrSkaAVDxMPFbLc27MANnU02T1q9ihn_hzEQ-dB WWpt1fi7hvW1dhA3Kk>
X-ME-Received: <xmr:bo1PZFbpdTAmE2wJpXWmOwxbcje9uLOX3BhzSTMrL1fLtTJzVqgF2Om4Lz6vZBUF6wb0dJrv_uuhOn4EGbuwRO141pbvZm6gGya4>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfedvgedgvddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtgffhggffkfhfjgfuvffosehtqh hmtdhhtdejnecuhfhrohhmpeevhhhrihhsthhophhhvghrucghohhougcuoegtrgifsehh vggrphhinhhgsghithhsrdhnvghtqeenucggtffrrghtthgvrhhnpeelgedvudevjeeule fglefgffffjeegtdfgfeevheehffegteduveevgedufedufeenucffohhmrghinhepihgv thhfrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homheptggrfieshhgvrghpihhnghgsihhtshdrnhgvth
X-ME-Proxy: <xmx:bo1PZMUJA4YmZrGQxvUuZzvgmRUFlKRdTYvNQtOc2giDLuOn3Gbc3Q> <xmx:bo1PZDnr8d0o4pMq4HM7UwKf0RzabD3rHuECTqq_MbftLQT6ZmdkHA> <xmx:bo1PZJf5yKAuTeaQm9XuFdWmyCAJSPglJcZutsdI_RwnW2w85YhVEg> <xmx:bo1PZJSP_cuRaqE0s9srn0tMg0pxNHMWXUmXvfh1_wMXCCEKGnEugA>
Feedback-ID: i2f494406:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <tls@ietf.org>; Mon, 1 May 2023 05:59:10 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Christopher Wood <caw@heapingbits.net>
Mime-Version: 1.0 (1.0)
Date: Mon, 01 May 2023 05:58:59 -0400
Message-Id: <C446C65E-924F-4927-BF53-E0B13EFC4930@heapingbits.net>
References: <FBE87FDA-A407-4DC8-A2E8-F39AB475C87B@heapingbits.net>
In-Reply-To: <FBE87FDA-A407-4DC8-A2E8-F39AB475C87B@heapingbits.net>
To: tls@ietf.org
X-Mailer: iPhone Mail (20E252)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/HAWpNpgptl--UZNSYuvsjB-Pc2k>
Subject: Re: [TLS] Consensus call on codepoint strategy for draft-ietf-tls-hybrid-design
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 01 May 2023 09:59:16 -0000

It looks like we have consensus for this strategy. We’ll work to remove codepoints from draft-ietf-tls-hybrid-design and then get experimental codepoints allocated based on draft-tls-westerbaan-xyber768d00.

Best,
Chris, for the chairs 

> On Mar 28, 2023, at 9:49 PM, Christopher Wood <caw@heapingbits.net> wrote:
> 
> As discussed during yesterday's meeting, we would like to assess consensus for moving draft-ietf-tls-hybrid-design forward with the following strategy for allocating codepoints we can use in deployments.
> 
> 1. Remove codepoints from draft-ietf-tls-hybrid-design and advance this document through the process towards publication.
> 2. Write a simple -00 draft that specifies the target variant of X25519+Kyber768 with a codepoint from the standard ranges. (Bas helpfully did this for us already [1].) Once this is complete, request a codepoint from IANA using the standard procedure.
> 
> The intent of this proposal is to get us a codepoint that we can deploy today without putting a "draft codepoint" in an eventual RFC.
> 
> Please let us know if you support this proposal by April 18, 2023. Assuming there is rough consensus, we will move forward with this proposal.
> 
> Best,
> Chris, Joe, and Sean
> 
> [1] https://datatracker.ietf.org/doc/html/draft-tls-westerbaan-xyber768d00-00