Re: [lamps] WGLC for draft-ietf-lamps-cms-sha3-hash

Daniel Van Geest <daniel.vangeest.ietf@gmail.com> Wed, 31 January 2024 14:21 UTC

Return-Path: <daniel.vangeest.ietf@gmail.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D091FC14F6BA for <spasm@ietfa.amsl.com>; Wed, 31 Jan 2024 06:21:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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=gmail.com
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 X1TdfmDBIR3s for <spasm@ietfa.amsl.com>; Wed, 31 Jan 2024 06:21:05 -0800 (PST)
Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 4A91CC14F696 for <spasm@ietf.org>; Wed, 31 Jan 2024 06:21:05 -0800 (PST)
Received: by mail-wm1-x32d.google.com with SMTP id 5b1f17b1804b1-40f037636cfso2134665e9.1 for <spasm@ietf.org>; Wed, 31 Jan 2024 06:21:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1706710863; x=1707315663; darn=ietf.org; h=content-language:thread-index:mime-version:message-id:date:subject :in-reply-to:references:to:from:from:to:cc:subject:date:message-id :reply-to; bh=9pxf5fm5O8e80CKrumpwpOWUMiS/XFt8o3tQ0vBZyVw=; b=mipM8B7RHA/Kl/KZVxD73u8q97qFAyem/taeDS/h1GmkMLpgGBzvIrvzIM/M1t8Mt3 UVHXMt+TLTBhwWP44J2XtrTMgd0iftZxyuL6CJuT//BL8Bxly2hhWoWp41wAlWSYK2B8 9bKHsWGL5didGS9aK2OZLyqpJV7w+CNMzi6AyWIwtRNLyhAdpqdbFS8Ft6URxZMsFTAW USUMF9zMdKcXHHpTU2HIKUbvtiJclvq31Jffnq9POIFLzh/IA//swArXEGjdN/dFTmM8 sbaq9WPBXPte46RipWXstpE+CPh2XbVbLSbwpto8dGBbWcQEiwV05ybgSqOjAs/Q4R+X tJ8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706710863; x=1707315663; h=content-language:thread-index:mime-version:message-id:date:subject :in-reply-to:references:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=9pxf5fm5O8e80CKrumpwpOWUMiS/XFt8o3tQ0vBZyVw=; b=vLjOEErx051eJ2qGd4EPxrwavT75YXIN1Uc17IRjfjUOBPSXGrQMa1C8EGAhL0osvS ULAFYMQNuTZd1M7wgsqDL4AcCO96GA0zlyu4BtpBPR53dd/P14nWoKG+hmR76KUhq2oV Qj/gH8F1TcpLONEztIb9o7e8m5HjMSUQHmQQevCUW1ib1Y38RgKFOAxaPb/SrTpYNpWG 2Mg1prSF8v2onu8RZQ51xPiNg+or5xyWq/90jUU3mhtdVaCojghJFE0ZPgJUzGAX7Yz5 Cxz+rfYkjEiTAaCqe54lAuOu6UmZh1NidJIamSDwYgjKBDx71T+qc+wd9wSuyzdARZhP vXpA==
X-Gm-Message-State: AOJu0YwbzUbH9dMHTtWG3UrehZ3TurN/2ERGhvWB3XdVV9AK0tDsGWuT Zo7tqSLiw8SA7g0uR7lc7IaS3RVC/ZUoUHLiHHnRPDTcKZ6EjGYIz2nMQigc
X-Google-Smtp-Source: AGHT+IGMyCPyHQHI3ABz0Q5Yzk7G219k2jmE2DzyuCJVkCBGgZW/WhyVfwPA1SbLT+W1aMuI1IbBKw==
X-Received: by 2002:adf:a14f:0:b0:33a:e3dd:490 with SMTP id r15-20020adfa14f000000b0033ae3dd0490mr1344930wrr.6.1706710863481; Wed, 31 Jan 2024 06:21:03 -0800 (PST)
X-Forwarded-Encrypted: i=0; AJvYcCXG5IeoopIjN+uOJ4xgtdmy7b72eGmwNRelsEOFhpatFkznj2IY3Hv4oxOqbnNm86cz9HnTlpfMVy6uc+UG9vnCVWzAWaAdUfwmOurbHxjrWeAXmDCwlP16bBtOqG0GRb9SUTOjl33RdGaujg==
Received: from DESKTOPUE07G7D ([2001:8a0:6a10:d300:a971:50c7:43ec:4948]) by smtp.gmail.com with ESMTPSA id u1-20020a05600c138100b0040f035bebfcsm1759740wmf.12.2024.01.31.06.21.02 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Jan 2024 06:21:03 -0800 (PST)
From: Daniel Van Geest <daniel.vangeest.ietf@gmail.com>
To: 'Mike Ounsworth' <Mike.Ounsworth=40entrust.com@dmarc.ietf.org>, 'Tim Hollebeek' <tim.hollebeek=40digicert.com@dmarc.ietf.org>, 'SPASM' <spasm@ietf.org>
References: <SN7PR14MB6492B10C0593B89D36FE221E837D2@SN7PR14MB6492.namprd14.prod.outlook.com> <CH0PR11MB573905E2C705F61F1529E63C9F7D2@CH0PR11MB5739.namprd11.prod.outlook.com>
In-Reply-To: <CH0PR11MB573905E2C705F61F1529E63C9F7D2@CH0PR11MB5739.namprd11.prod.outlook.com>
Date: Wed, 31 Jan 2024 14:21:04 -0000
Message-ID: <09a101da5450$b9e4afe0$2dae0fa0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_09A2_01DA5450.B9E4AFE0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQG78XSjZkq1rD4S//IRAb8A1H/1VADUHj+vsSoTgYA=
Content-Language: en-ca
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/X7h2x5aMVoNOCKUuorQ5sBXLR2I>
Subject: Re: [lamps] WGLC for draft-ietf-lamps-cms-sha3-hash
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: This is the mail list for the LAMPS Working Group <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jan 2024 14:21:09 -0000

These will be useful for KEMRI with ML-KEM since it uses lots of variants of
SHA3 and SHAKE under the covers so we will want a KDF using at least one of
those.

 

While going over the draft I just found a few nits:

 

Section 3.1:

Trailing braces on the following line:kmac

                The RSASSA PKCS#1 v1.5 is defined in [RFC8017]}}.

 

Section 5.1:

"algorithm" is misspelled:

                [I-D.ietf-lamps-cms-kemri] is one place where algrithim
identifiers

 

Section 6:

Remove either "cryptographics" or "such" from the following line:

number generators (PRNGs) to generate cryptographic such values can

 

The id-alg-hkdf-with-sha3-* object identifiers are currently TBD.  Since
cms-kemri and cms-kyber implementation and interop is going on right now in
the hackathon group, it would be nice to have those assigned.  Is it too
late for early assignment?  Is it too early for normal assignment?  I don't
know if those OIDs will be the ones recommended by cms-kyber, but it would
be nice to have some OIDs for specs that aren't paywalled (kdf2, kdf3).

 

Thanks,

Daniel

 

 

From: Spasm <spasm-bounces@ietf.org> On Behalf Of Mike Ounsworth
Sent: Tuesday, January 30, 2024 9:10 PM
To: Tim Hollebeek <tim.hollebeek=40digicert.com@dmarc.ietf.org>; SPASM
<spasm@ietf.org>
Subject: Re: [lamps] WGLC for draft-ietf-lamps-cms-sha3-hash

 

Ship it!

 

---

Mike Ounsworth

 

From: Spasm <spasm-bounces@ietf.org <mailto:spasm-bounces@ietf.org> > On
Behalf Of Tim Hollebeek
Sent: Tuesday, January 30, 2024 2:43 PM
To: SPASM <spasm@ietf.org <mailto:spasm@ietf.org> >
Subject: [EXTERNAL] [lamps] WGLC for draft-ietf-lamps-cms-sha3-hash

 

Hello,

 

Russ has suggested that draft-ietf-lamps-cms-sha3-hash might be ready for
WGLC, and since it's a pretty simple draft that seems like a pretty
reasonable way to flush out any remaining comments and problems.

 

Therefore this is the WGLC for draft-ietf-lamps-cms-sha3-hash:

 

Use of the SHA3 One-way Hash Functions in the Cryptographic Message Syntax
(CMS)

https://datatracker.ietf.org/doc/draft-ietf-lamps-cms-sha3-hash/

 

Abstract

 

   This document describes the conventions for using the four one-way

   hash functions in the SHA3 family with the Cryptographic Message

   Syntax (CMS).

 

Please send comments to the list by 12 February 2024.

 

-Tim