[lamps] Re: WGLC for draft-ietf-lamps-cms-sphincs-plus
Carl Wallace <carl@redhoundsoftware.com> Tue, 01 October 2024 11:37 UTC
Return-Path: <carl@redhoundsoftware.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 65757C151552 for <spasm@ietfa.amsl.com>; Tue, 1 Oct 2024 04:37:39 -0700 (PDT)
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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=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 (1024-bit key) header.d=redhoundsoftware.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 99BDZhb6tVbM for <spasm@ietfa.amsl.com>; Tue, 1 Oct 2024 04:37:35 -0700 (PDT)
Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48BC9C169406 for <spasm@ietf.org>; Tue, 1 Oct 2024 04:37:34 -0700 (PDT)
Received: by mail-qt1-x82e.google.com with SMTP id d75a77b69052e-45815723c87so42670441cf.0 for <spasm@ietf.org>; Tue, 01 Oct 2024 04:37:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhoundsoftware.com; s=google; t=1727782654; x=1728387454; darn=ietf.org; h=mime-version:in-reply-to:references:thread-topic:message-id:cc:to :from:subject:date:user-agent:from:to:cc:subject:date:message-id :reply-to; bh=9yFlYB4GpbVJP80p6ggGaequI2p8ub22YRQaQg5XCfQ=; b=CtlnUhl5WBe4uB9OzQ24GW4jrbxt+CCUbIcLqABlgDXj7yIk48x6EPPOCVnmQ5ZVY2 BOZbMOPoVXAv0VZiwW9XSlaXCkIdGHNIZFOhgC+ImpTTubyp9ktovlHDslGrExzKJ+4O zynYTHBEPHoEVB/x3etjl+ywCAjCUdXGaWzXs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727782654; x=1728387454; h=mime-version:in-reply-to:references:thread-topic:message-id:cc:to :from:subject:date:user-agent:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=9yFlYB4GpbVJP80p6ggGaequI2p8ub22YRQaQg5XCfQ=; b=HczkFcZCosa9rSDtmub60BSrPre5/pjeRTnrl5IUYnu5JIlgC6Oicj22WL0i27qk+w n1RUSxJgSPwBJ1tqgfg2yrpXGploDIFS5SPAlI1TxZwl026Vxwl0vc+CBarza0PNPhGo 1JUTWi97sHNhrOw2i1SC4EARNFBpjF2GEjI+8cFf4dCg/KlcPv28kDgFr2oNfjmRrl+m lbc1pVEzhKK85YxV8OgD9fFnPZezmgQvfgyW2txPaAIuRVlCHFWUoBgQLBD+km8008kU VyQ6982Jg+FXVzzzFV05Xz961QJzoR99qYBbJbWPP+9otGTjKqIIPPOos2XigE48/9ao 9Qfw==
X-Gm-Message-State: AOJu0YxX5jaEt/3iipKGa1i7j9IvW9+5zsESyVtuhcftXa8sGmH9nQEB Ll98vOoDMFa2hI55PD1ltnAz3d4SI9yYV9gLPXJoqztnp+40HAmx55DU/oHAeqjiIU37CPPUzwa I
X-Google-Smtp-Source: AGHT+IF6yb+lbFJYli02M56SfzqiSBvSD89QQ4yhsgSivtQKF/XGunE8GLx79QbRaMrt8rYGAKIYVA==
X-Received: by 2002:a05:622a:1483:b0:458:611b:ac34 with SMTP id d75a77b69052e-45d73a6e8ccmr44118531cf.12.1727782653781; Tue, 01 Oct 2024 04:37:33 -0700 (PDT)
Received: from [192.168.4.77] (pool-96-255-232-167.washdc.fios.verizon.net. [96.255.232.167]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-45c9f2bd61bsm44646461cf.35.2024.10.01.04.37.31 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Oct 2024 04:37:32 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/16.89.24092212
Date: Tue, 01 Oct 2024 07:37:31 -0400
From: Carl Wallace <carl@redhoundsoftware.com>
To: Russ Housley <housley@vigilsec.com>
Message-ID: <24BFF03A-AB52-49BF-8298-4EDA48622BCC@redhoundsoftware.com>
Thread-Topic: [lamps] WGLC for draft-ietf-lamps-cms-sphincs-plus
References: <9BC9C8A3-554F-493A-8D4B-E3D2BEFC3D22@redhoundsoftware.com> <DCEFA353-6397-4DA3-82BB-9596EA6D49BF@vigilsec.com>
In-Reply-To: <DCEFA353-6397-4DA3-82BB-9596EA6D49BF@vigilsec.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3810613051_4254336488"
Message-ID-Hash: T3PI5HINYVS4MSB2RTK4D6SCHHQFJDX7
X-Message-ID-Hash: T3PI5HINYVS4MSB2RTK4D6SCHHQFJDX7
X-MailFrom: carl@redhoundsoftware.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-spasm.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: SPASM <spasm@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [lamps] Re: WGLC for draft-ietf-lamps-cms-sphincs-plus
List-Id: This is the mail list for the LAMPS Working Group <spasm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/FzS5_xVjA-GLp5w6Nhy6eOGlXHU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Owner: <mailto:spasm-owner@ietf.org>
List-Post: <mailto:spasm@ietf.org>
List-Subscribe: <mailto:spasm-join@ietf.org>
List-Unsubscribe: <mailto:spasm-leave@ietf.org>
Those changes look good to me. Thanks, Russ. From: Russ Housley <housley@vigilsec.com> Date: Monday, September 30, 2024 at 5:12 PM To: Carl Wallace <carl@redhoundsoftware.com> Cc: SPASM <spasm@ietf.org> Subject: Re: [lamps] WGLC for draft-ietf-lamps-cms-sphincs-plus Thanks for the review, Carl. In the introduction, change predigest to pre-hash to match FIPS 205 Done. I caught this mistake when handling the last comment from Daniel's review. Add some words re: decision to support on pure mode. Section 6 is likely where this would fit. Section 6 now reads: If slh_sign is implemented in a hardware device such as hardware security module (HSM) or portable cryptographic token, implementations might want to avoid is sending the full content to the device. By including signed attributes, which necessarily include the message-digest attribute and the content-type attribute as described in Section 5.3 of [RFC5652], the much smaller set of signed attributes are sent to the device for signing. Following the approach in the previous paragraph is essentially the same as using SLH-DSA in pre-hash mode, which means that a hash of the content is passed to the SLH-DSA signature operation instead of the full message content. For this reason, this document only specifies the use od SLH-DSA pure mode. Add “algorithms” to the end of the second sentence in section 1.2 Done. In the following paragraph, I also changed "large-scale quantum computers" to "cryptographically relevant quantum computers (CRQC)" to align with the terms in PQUIP. Russ
- [lamps] WGLC for draft-ietf-lamps-cms-sphincs-plus Tim Hollebeek
- [lamps] Re: WGLC for draft-ietf-lamps-cms-sphincs… Daniel Van Geest
- [lamps] Re: WGLC for draft-ietf-lamps-cms-sphincs… Russ Housley
- [lamps] Re: WGLC for draft-ietf-lamps-cms-sphincs… Russ Housley
- [lamps] Re: WGLC for draft-ietf-lamps-cms-sphincs… Daniel Van Geest
- [lamps] Re: WGLC for draft-ietf-lamps-cms-sphincs… Daniel Van Geest
- [lamps] Re: WGLC for draft-ietf-lamps-cms-sphincs… Russ Housley
- [lamps] Re: WGLC for draft-ietf-lamps-cms-sphincs… Daniel Van Geest
- [lamps] Re: WGLC for draft-ietf-lamps-cms-sphincs… Falko Strenzke
- [lamps] Re: WGLC for draft-ietf-lamps-cms-sphincs… Markku-Juhani O. Saarinen
- [lamps] Re: WGLC for draft-ietf-lamps-cms-sphincs… Tim Hollebeek
- [lamps] Re: WGLC for draft-ietf-lamps-cms-sphincs… Carl Wallace
- [lamps] Re: WGLC for draft-ietf-lamps-cms-sphincs… Russ Housley
- [lamps] Re: WGLC for draft-ietf-lamps-cms-sphincs… Carl Wallace