IETF Logo Mail Archive

Re: [Pqc] [Ext] [EXTERNAL] Re: [lamps] CMS Kyber: include PK and CT in the KDF?

Paul Hoffman <paul.hoffman@icann.org> Thu, 11 April 2024 22:45 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: pqc@ietfa.amsl.com
Delivered-To: pqc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 276A9C14F6BD; Thu, 11 Apr 2024 15:45:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 NKiqMRzaD5v0; Thu, 11 Apr 2024 15:45:05 -0700 (PDT)
Received: from ppa3.lax.icann.org (ppa3.lax.icann.org [192.0.33.78]) (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 A50BCC14F68C; Thu, 11 Apr 2024 15:45:05 -0700 (PDT)
Received: from MBX112-E2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.7]) by ppa3.lax.icann.org (8.17.1.24/8.17.1.24) with ESMTPS id 43BMj3qh006333 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 11 Apr 2024 22:45:03 GMT
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.28; Thu, 11 Apr 2024 15:45:02 -0700
Received: from MBX112-W2-CO-1.pexch112.icann.org ([169.254.44.235]) by MBX112-W2-CO-1.pexch112.icann.org ([169.254.44.235]) with mapi id 15.02.1258.028; Thu, 11 Apr 2024 15:45:02 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Deirdre Connolly <durumcrustulum@gmail.com>
CC: LAMPS <spasm@ietf.org>, "pqc@ietf.org" <pqc@ietf.org>
Thread-Topic: [Ext] [Pqc] [EXTERNAL] Re: [lamps] CMS Kyber: include PK and CT in the KDF?
Thread-Index: AQHajF66WJgHpaveUEaz3qe22WKX6bFkHcIAgAACoAA=
Date: Thu, 11 Apr 2024 22:45:02 +0000
Message-ID: <630EA55F-D9F5-4819-B13A-9F0BEF676B62@icann.org>
References: <CAFR824w0rBfxGzCJrSZ3f45Lyn7SEVLZK6cM9ZaZVHVPujs-5g@mail.gmail.com> <A31C1C09-297F-4C4A-837E-FD2A703AD96F@vigilsec.com> <CH0PR11MB57391B1E18D87AEB8D9519EE9F052@CH0PR11MB5739.namprd11.prod.outlook.com> <CAFR824ybzCDY-C1cXFHcUhgZ-m8wgqgw4eCNoCraX7sPNNxC6g@mail.gmail.com> <C0BE506D-9740-43FE-8E6E-75D8972A6CB6@icann.org> <CAFR824wjguW_dp=C87gSir_uS76p5rKT8sT15ZSQMMCykiHrEg@mail.gmail.com>
In-Reply-To: <CAFR824wjguW_dp=C87gSir_uS76p5rKT8sT15ZSQMMCykiHrEg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.32.234]
x-source-routing-agent: True
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E52BA0011D07D54E99A53DFB32F6D101@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.1011,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2024-04-11_11,2024-04-09_01,2023-05-22_02
Archived-At: <https://mailarchive.ietf.org/arch/msg/pqc/5hFvS9Rzfw_oDT9LH2BHaaNMcy8>
Subject: Re: [Pqc] [Ext] [EXTERNAL] Re: [lamps] CMS Kyber: include PK and CT in the KDF?
X-BeenThere: pqc@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Post Quantum Cryptography discussion list <pqc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pqc>, <mailto:pqc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pqc/>
List-Post: <mailto:pqc@ietf.org>
List-Help: <mailto:pqc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pqc>, <mailto:pqc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2024 22:45:06 -0000

On Apr 11, 2024, at 15:35, Deirdre Connolly <durumcrustulum@gmail.com> wrote:

> They said they plan to:

Yes, indeed. "plan to" is different than "will make". Dustin Moody from NIST said on the forum mailing list:

> We welcome feedback on the topics mentioned on these slides.  We also intend to have some posts next week on the pqc-forum which will expound on these slides for those who were unable to attend the conference. 
> 
> We do NOT plan to have another draft for any of ML-KEM, ML-DSA, or SLH-DSA.  That is, we will publish the final versions of these standards as the next step.  We expect to publish them this summer.  So please give us any feedback sooner than later.  

I interpret this as that they plan to unless the ensuing discussion shows them why they should not.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email