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:22 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 BCB9FC14F6E9; Thu, 11 Apr 2024 15:22:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 BA-fqBDVWpmQ; Thu, 11 Apr 2024 15:22:27 -0700 (PDT)
Received: from ppa4.dc.icann.org (ppa4.dc.icann.org [192.0.46.77]) (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 86A12C14F5FC; Thu, 11 Apr 2024 15:22:27 -0700 (PDT)
Received: from MBX112-W2-CO-2.pexch112.icann.org (out.mail.icann.org [64.78.33.6]) by ppa4.dc.icann.org (8.17.1.24/8.17.1.24) with ESMTPS id 43BMM27i020134 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 11 Apr 2024 15:22:02 -0700
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:22:23 -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:22:23 -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: AQHajF65Od8GWsbO+ki7QqJT+yuMrQ==
Date: Thu, 11 Apr 2024 22:22:23 +0000
Message-ID: <C0BE506D-9740-43FE-8E6E-75D8972A6CB6@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>
In-Reply-To: <CAFR824ybzCDY-C1cXFHcUhgZ-m8wgqgw4eCNoCraX7sPNNxC6g@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: <8708CBB2A78113439B4D02E7DA7A8CB7@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_10,2024-04-09_01,2023-05-22_02
Archived-At: <https://mailarchive.ietf.org/arch/msg/pqc/vdxE9V0TU-nv41bdXYxgqGl0JQw>
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:22:29 -0000

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

> NIST has just announced they will make . . .

A possibly-important correction: they announced that they *may* make the changes listed today. They said they will be documenting their intention soon, and will explicitly ask for public comments on the changes.

Of course, if one or more of the changes they propose to make is good for IETF WGs, it would be good if people respond to their request for comments.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email