IETF Logo Mail Archive

Re: [lamps] I-D Action: draft-ietf-lamps-cms-sha3-hash-01.txt

Daniel Van Geest <daniel.vangeest.ietf@gmail.com> Fri, 01 March 2024 21: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 CF7B9C14F693 for <spasm@ietfa.amsl.com>; Fri, 1 Mar 2024 13:21:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, 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_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 Bkx9lPoYxcj7 for <spasm@ietfa.amsl.com>; Fri, 1 Mar 2024 13:21:28 -0800 (PST)
Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (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 1E94DC14F614 for <spasm@ietf.org>; Fri, 1 Mar 2024 13:21:28 -0800 (PST)
Received: by mail-wr1-x435.google.com with SMTP id ffacd0b85a97d-33db19538d0so299152f8f.1 for <spasm@ietf.org>; Fri, 01 Mar 2024 13:21:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1709328086; x=1709932886; darn=ietf.org; h=content-language:thread-index:content-transfer-encoding :mime-version:message-id:date:subject:in-reply-to:references:to:from :from:to:cc:subject:date:message-id:reply-to; bh=brjnLtIbSRM5nU4hmP4IJDM87DgtR/8sGk6OgM3Knnc=; b=afhR+kNgbPuDUDXxgCD6Fh3ooPq4swDLwooLXq8EgylEuFUnaABdTcZdjY0Cyw0+PQ V6tJZyrN0OfE4mwdCGx72tbvEhrS8VZm1tpmlAC3lkb0zQQhgNlKofFHpqOvhdVFv6tO ZViEdwesBuaF0cIqzjb+u/qt+DDlurAKMzcrvA6pOrywFze+Z0t5s/jKvqYXCb+7HrFr U+igwugXvIz4WfQl8JG8sRbt5VjA4+oqG4oLtJ8Cu6C+LmsKvSaHt6EiPKRrUNkAk1+N GEFo+rr7NW8/XfhIT2JtykLgJsv2T9dZzH7T8la85Rizw/ObNib4g0JosFL5iI1Mzb+T 3GhQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709328086; x=1709932886; h=content-language:thread-index:content-transfer-encoding :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=brjnLtIbSRM5nU4hmP4IJDM87DgtR/8sGk6OgM3Knnc=; b=s3YQ/eGHhEvcGhk39SPUSSCr6u18yzrD/YRlvYoy19V3cHie5DupWQIOqm1ByoAsJy k/lGB/UMA/p6ji2dAf/S2K4WwQuPmHHoRnp78KLp1DKF5r9G47m1/hFFf4OCchi7Txdi yEvcHjDS5ll3aDK8J3r/cQhljAkofehr/XxgGzbH2MnYhR5ewrjzksZO0POQGwdHuvoa ONgZMd8rQWq3gClpIrqbYrRoxygXvKPtyHa8lvdhLpLg6muTh1sCFE3OyJW3dNvqflnB X6FZKTWA323kdbuMP0J/Q9eybxgmAI6pMUht6tqZljWvhbSbeOh/LEpYpGCPAR2uwh5D pAWQ==
X-Forwarded-Encrypted: i=1; AJvYcCXWjMtuH6KM/fcUmohlcjmoufEQ5Xc3W+wN9m0NjyOQppQAGQqtQmahaTsRC784MgVvcz8j4f8/kEKUTzi/vw==
X-Gm-Message-State: AOJu0YzjXxizh8M8BMnLHIDfGy5WMWseYUJBT6bBII0y1fJdKWoIbxT8 chTenYwXj16x7drd5PV32Xac2w9ovDZvFEqObBn1QEjJLgaygihqtlOfMM+u
X-Google-Smtp-Source: AGHT+IGYeTxsXjHGzl1svpHz/INFUZn0YjUiCH9lepl3fGVforOE40ovqjbJYPwn+kvApO3AH14ujQ==
X-Received: by 2002:a05:600c:3b25:b0:412:b2af:2632 with SMTP id m37-20020a05600c3b2500b00412b2af2632mr2380810wms.0.1709328085808; Fri, 01 Mar 2024 13:21:25 -0800 (PST)
Received: from DESKTOPUE07G7D ([2001:8a0:6a10:d300:2a0:a513:16c9:5800]) by smtp.gmail.com with ESMTPSA id h7-20020a05600c314700b00412b431eb0csm6585414wmo.14.2024.03.01.13.21.25 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Mar 2024 13:21:25 -0800 (PST)
From: Daniel Van Geest <daniel.vangeest.ietf@gmail.com>
To: 'Russ Housley' <housley@vigilsec.com>, 'LAMPS' <spasm@ietf.org>
References: <170932438014.22799.12059202425488054847@ietfa.amsl.com> <759567E5-BC43-4FE7-8DE1-6B6449F39CCE@vigilsec.com>
In-Reply-To: <759567E5-BC43-4FE7-8DE1-6B6449F39CCE@vigilsec.com>
Date: Fri, 01 Mar 2024 21:21:25 -0000
Message-ID: <083a01da6c1e$6ad60300$40820900$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGMH1KgnXvxvLjhkyR+BRRWhaJqBQI3ypnbsa495dA=
Content-Language: en-ca
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/ikzjf4GZf9DTEu8EDM6mUFcfHlk>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-cms-sha3-hash-01.txt
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: Fri, 01 Mar 2024 21:21:31 -0000

Thanks Russ,

	   When the id-kmac128 or id-kmac256 is used as part of an algorithm

 	   identifier, the parameters field MUST be absent if no
customization	
 	   label is used for S.  If any other value is used for S, then	
 	   parameters field MUST be present and contain the value of S,
encoded	
 	   as Customization.

Maybe it doesn't matter because this has been specified by NIST and there's
nothing to be done about it, but couldn't it be the case that the protocol
specifies the customization label, and so it would be unnecessary to include
the customization label in the parameters.  For example, cms-kyber could
specify that the customization label is always "cms-kyber", in which case
encoding this in the algorithm identifier is redundant.

Thanks,
Daniel


-----Original Message-----
From: Spasm <spasm-bounces@ietf.org> On Behalf Of Russ Housley
Sent: Friday, March 1, 2024 8:32 PM
To: LAMPS <spasm@ietf.org>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-cms-sha3-hash-01.txt

As requested, the OIDs for KMAC as a KDF have been added.

I am not aware of any remaining open issues.

Russ


> On Mar 1, 2024, at 3:19 PM, internet-drafts@ietf.org wrote:
> 
> Internet-Draft draft-ietf-lamps-cms-sha3-hash-01.txt is now available. 
> It is a work item of the Limited Additional Mechanisms for PKIX and 
> SMIME (LAMPS) WG of the IETF.
> 
>   Title:   Use of the SHA3 One-way Hash Functions in the Cryptographic
Message Syntax (CMS)
>   Author:  Russ Housley
>   Name:    draft-ietf-lamps-cms-sha3-hash-01.txt
>   Pages:   20
>   Dates:   2024-03-01
> 
> Abstract:
> 
>   This document describes the conventions for using the one-way hash
>   functions in the SHA3 family with the Cryptographic Message Syntax
>   (CMS).  The SHA3 family can be used as a message digest algorithm, as
>   part of a signature algorithm, as part of a message authentication
>   code, or part of a key derivation function.
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-lamps-cms-sha3-hash/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-lamps-cms-sha3-hash-01.html
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-lamps-cms-sha3-ha
> sh-01
> 
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts

_______________________________________________
Spasm mailing list
Spasm@ietf.org
https://www.ietf.org/mailman/listinfo/spasm

v2.23.0 | Report a Bug | By Email