IETF Logo Mail Archive

[lamps] Re: [IANA #1448907] expert review for draft-ietf-lamps-cms-composite-sigs (smi-numbers)

Russ Housley <housley@vigilsec.com> Tue, 31 March 2026 17:16 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@mail2.ietf.org
Delivered-To: spasm@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 8EA26D437F95 for <spasm@mail2.ietf.org>; Tue, 31 Mar 2026 10:16:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1774977419; bh=IOgEEzsJ4+yrnUepbG7GxEansY5SyCbksg/dWIWH/MY=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=O5ufzN/aCpwmIiEggdBOqqr5cHcVnhTTMNaYaLnphSi8U8JGZVTjkG+5sYicLh5iq YMzAGXB84uY0zLxLKQHUtz9s+yHWxeGgMWmrx1tzLnkRoQw6SBUsxhzYbDs5wDAHca xX3hPtRJ8DHLGeZC01/i6zKjfCTd60CeuWZr+fNs=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=vigilsec.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aE2keTklvPfI for <spasm@mail2.ietf.org>; Tue, 31 Mar 2026 10:16:58 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id DEABDD437F89 for <spasm@ietf.org>; Tue, 31 Mar 2026 10:16:58 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id A5ED51A0FF1; Tue, 31 Mar 2026 13:16:58 -0400 (EDT)
Received: from smtpclient.apple (pool-96-255-71-95.washdc.fios.verizon.net [96.255.71.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 852FB1A14AE; Tue, 31 Mar 2026 13:16:58 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <BEDFDD83-5080-489C-B6B3-3D477935A16F@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_BAD0F3CB-1712-4A52-90CA-A869A608599C"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.400.21\))
Date: Tue, 31 Mar 2026 13:16:48 -0400
In-Reply-To: <rt-5.0.3-1140405-1774976055-1002.1448907-9-0@icann.org>
To: drafts-expert-review-comment@iana.org
References: <RT-Ticket-1448907@icann.org> <rt-5.0.3-1053960-1774902366-491.1448907-9-0@icann.org> <rt-5.0.3-1140405-1774976055-1002.1448907-9-0@icann.org>
X-Mailer: Apple Mail (2.3864.400.21)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vigilsec.com; h=from:message-id:content-type:mime-version:subject:date:in-reply-to:cc:to:references; s=pair-202402141609; bh=kVh9ESuH+KDxL3x7B/jA+ShEZvcukRCoGPfwz5rk2K8=; b=QwAtHCnvHgXtz5ku9lNngS0QUxAbhbcHiKry4KxQkEubYCysxY9LPMh6KdWLIXkTzenE8ll+HwI+WYSADJcq06gYPM9RuSbdNEagVdCUDwZ03wdjXVGEDiWNxhVtVdCLY4IWphAKDSik7299C2xG//+QXCiGIygrlic3ERkfY+ViQoAxpsEzg0xCRSF4X/5AXfu0/uZBoWUiBz7NqOHrLkny2VOqfaZYzlhwHBxLrRnrw8U9CkfghdsBQey61+SqiocCJCcBqJVnGUkjsHJvE0y8B7BHSX3mVseefVXoazVegB4cQNhbtow9fVLv4LBvkLzCXcGYTd/FmHg9a6Lv6A==
X-Scanned-By: mailmunge 3.09
Message-ID-Hash: HISSBH2G6RXW57GKG3RDG5TXGLZSAGQN
X-Message-ID-Hash: HISSBH2G6RXW57GKG3RDG5TXGLZSAGQN
X-MailFrom: housley@vigilsec.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: Sean Turner <sean@sn3rd.com>, IETF LAMPS <spasm@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [lamps] Re: [IANA #1448907] expert review for draft-ietf-lamps-cms-composite-sigs (smi-numbers)
List-Id: This is the mail list for the LAMPS Working Group <spasm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/Ldmb2RmR9U9o1zSga3cWlzlQ54A>
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>

David:

It looks god to me.  I am the document shepherd for this one, so I had already review the IANA Considerations.

The algorithm identifiers have already been assigned.

The only OID that needs to be assigned is the module identifier, which should be assigned here:

   https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-1.3.6.1.5.5.7.0

Russ

> On Mar 31, 2026, at 12:54 PM, David Dong via RT <drafts-expert-review-comment@iana.org> wrote:
> 
> Dear Russ Housley, Sean Turner (cc: lamps wg),
> 
> As the designated experts for the SMI Security for PKIX Module Identifier registry, can you review the proposed registration in draft-ietf-lamps-cms-composite-sigs-04 for us? Please see
> 
> https://datatracker.ietf.org/doc/draft-ietf-lamps-cms-composite-sigs/
> 
> The due date is April 14th.
> 
> If this is OK, when the IESG approves the document for publication, we'll make the registration at:
> 
> https://www.iana.org/assignments/smi-numbers/
> 
> Unless you ask us to wait for the other reviewer, we’ll act on the first response we receive.
> 
> With thanks,
> 
> David Dong
> IANA Services Sr. Specialist

v2.46.0 | Report a Bug | By Email | System Status