Re: [lamps] [EXTERNAL] Re: Call for Adoption of draft-gazdag-x509-slhdsa and draft-gazdag-x509-shbs

Daniel Van Geest <daniel.vangeest.ietf@gmail.com> Thu, 21 March 2024 14:18 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 E46E8C18DB90 for <spasm@ietfa.amsl.com>; Thu, 21 Mar 2024 07:18:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.106
X-Spam-Level:
X-Spam-Status: No, score=-1.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, FREEMAIL_REPLY=1, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no 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 8VMIX8Ywdqse for <spasm@ietfa.amsl.com>; Thu, 21 Mar 2024 07:18:53 -0700 (PDT)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (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 8717CC180B7C for <spasm@ietf.org>; Thu, 21 Mar 2024 07:18:53 -0700 (PDT)
Received: by mail-lj1-x229.google.com with SMTP id 38308e7fff4ca-2cd3aea2621so2376901fa.1 for <spasm@ietf.org>; Thu, 21 Mar 2024 07:18:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711030732; x=1711635532; 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=NDio3Il9Ao1lCPgDk6ugAfIZ7s+XIQLazfANaMNsI44=; b=MGvNY7Qb89H1zEuQFhNhvkv2rFMqH0xscQBc42hTXneH6TCgEFUc2aimH/rCgbYl7B 5fvh9tl/C5Xe45NEy8fGrBBEo5wx3A+IUlYPeeHgCYrertHH5n+8PzHg+xfZLxIixrGN wP8KHo85RwsROn0EOSd3FGbOFFVyg50pprc2H9xHWOUz+wbxos1BOO2AAmr9A8znM04+ RlqNLKHwdXg1bP3+6ZdfVyQTxx099AR2aif59y/BIK6+NcKw8TVYVtHz+D22uN4QOueZ 7Mwo8tEL458pU/Zj/LlYaxHd8NPi1rjmzba5i7pC7zmO+WwdhTV2O02e2OhWHhyR3SZG +Mmg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711030732; x=1711635532; 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=NDio3Il9Ao1lCPgDk6ugAfIZ7s+XIQLazfANaMNsI44=; b=Alnp0EKMjOuRKcQsi6pkdrFP2MjdQK4VZx2+yGWUMUBTFnDdT7ppO4knxoPi/1KhRC ZuVJYb1ke3TcGrkfqmbUicC3+nFIgpQ1URRJx9ZStrW9BqbZFNo2OZd1bzNXH9K9tC+o Hq0/AJrPNWxltJWzUvI5b5UODQ4i4q3N4CXms/zq+qGofRTd7kcnHaSfLPUOIYIoIBnV 8b0A7PuK1lYAdYw8huPes41Ca6EPQnLqaJZJOgtkDfAyLB8qwYZuGeYmSb/WG0U9on2O v0IneAKj0ep0uVM5+M0oR58VtF7ozcbwPNb4D8/TO98W/Dnsd5/1Nw8Bu5ljUIobnoOS ELHg==
X-Forwarded-Encrypted: i=1; AJvYcCV89aKZ3oTCZ5S9KJ8Gtrx+LBcbIFKrAagxG3gxu0NP09551p95/o6fg+gPdy4Bx14mKRTNhipsIY3PL9Cg7Q==
X-Gm-Message-State: AOJu0YwHk0nwNyi39lA9filLcPA1SXbWStM3dSqJFaxJ9J6lfm8wCYb+ WtytLKq/qcoa4Jr3yr1yMmqfnQXyIBzEx1HW4EtQRBHJEuqKZ/zZ
X-Google-Smtp-Source: AGHT+IFL533H1vKkeT7icAGaUlSPZsx4YoMDU9SAz7ZchP5VWXTc4C8O3tx7n4c7+8l3Np4ecHw1iQ==
X-Received: by 2002:a2e:914a:0:b0:2d2:246e:b373 with SMTP id q10-20020a2e914a000000b002d2246eb373mr5993197ljg.5.1711030731417; Thu, 21 Mar 2024 07:18:51 -0700 (PDT)
Received: from DESKTOPUE07G7D ([2001:8a0:6a10:d300:2a0:a513:16c9:5800]) by smtp.gmail.com with ESMTPSA id y25-20020a05600c365900b00413fda042ddsm2231852wmq.0.2024.03.21.07.18.50 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Mar 2024 07:18:50 -0700 (PDT)
From: Daniel Van Geest <daniel.vangeest.ietf@gmail.com>
To: 'Mike Ounsworth' <Mike.Ounsworth=40entrust.com@dmarc.ietf.org>, 'Rohan Mahy' <rohan.ietf@gmail.com>, spasm@ietf.org
References: <CAKoiRuYsiX9UUEb9CTnnYoeLOLAGn20vTO3JJF9rU9bCvMvi-Q@mail.gmail.com> <CH0PR11MB5739477C7E24DB64C4B5E4D69F322@CH0PR11MB5739.namprd11.prod.outlook.com>
In-Reply-To: <CH0PR11MB5739477C7E24DB64C4B5E4D69F322@CH0PR11MB5739.namprd11.prod.outlook.com>
Date: Thu, 21 Mar 2024 14:18:52 -0000
Message-ID: <01de01da7b9a$b400c3e0$1c024ba0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01DF_01DA7B9A.B400C3E0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQLmWoMEtk9C0zpCrpXlpHOGCmEC+wHWl+YRrxu1BNA=
Content-Language: en-ca
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/2AhYZXF6teziphqLNjo7QmPfG_c>
Subject: Re: [lamps] [EXTERNAL] Re: Call for Adoption of draft-gazdag-x509-slhdsa and draft-gazdag-x509-shbs
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: Thu, 21 Mar 2024 14:18:58 -0000

I can’t speak to the current state of things, but my very first email
regarding draft-vangeest-x509-hash-sigs in 2018 said:

 

id-alg-hss-lms-hashsig is repeated from ietf-lamps-cms-hash-sig.  All other
OIDs are assigned from ISARA’s arc.  If instead there is a preferred arc to
request OIDs from we can look into that.

 

And at the time when I said “look into that”  I meant “just do it”.

 

One problem with a single OID for XMSS (and the same applies to HSS) is that
there are a whole bunch of parameters registered (and possibly more to
come).  Do we really want a single OID registered for all the parameters?
What if someone only wants to implement a subset of them?  If a new set of
parameters are added do we assign a new OID?  Do we want to add Object
Identifier parameters to the XMSS OID?  That ship has sailed already for
HSS…

 

Daniel

 

 

 

From: Spasm <spasm-bounces@ietf.org> On Behalf Of Mike Ounsworth
Sent: Thursday, March 21, 2024 12:03 PM
To: Rohan Mahy <rohan.ietf@gmail.com>; spasm@ietf.org
Subject: Re: [lamps] [EXTERNAL] Re: Call for Adoption of
draft-gazdag-x509-slhdsa and draft-gazdag-x509-shbs

 

I support adoption of both since any FIPS-approved algorithm should be
usable in X.509.

 

My only question is whether there a strong reason for using proprietary
(ISARA) OIDs for XMSS and XMSS^MT in the RFC rather than getting new ones
from IANA? Is there a significant install base that is already deployed on
this OID?

 

- Mike Ounsworth

  _____  

From: Spasm <spasm-bounces@ietf.org <mailto:spasm-bounces@ietf.org> > on
behalf of Rohan Mahy <rohan.ietf@gmail.com <mailto:rohan.ietf@gmail.com> >
Sent: Thursday, March 21, 2024 9:47:15 PM
To: spasm@ietf.org <mailto:spasm@ietf.org>  <spasm@ietf.org
<mailto:spasm@ietf.org> >
Subject: [EXTERNAL] Re: [lamps] Call for Adoption of
draft-gazdag-x509-slhdsa and draft-gazdag-x509-shbs 

 

I support adoption of draft-gazdag-x509-slhdsa. I have no objection to
adoption of draft-gazdag-x509-shbs. Thanks, -rohan  ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍
‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍
‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍
‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ 

I support adoption of draft-gazdag-x509-slhdsa. 

 

I have no objection to adoption of draft-gazdag-x509-shbs.

 

Thanks,

-rohan 

Any email and files/attachments transmitted with it are intended solely for
the use of the individual or entity to whom they are addressed. If this
message has been sent to you in error, you must not copy, distribute or
disclose of the information it contains. Please notify Entrust immediately
and delete the message from your system.