[lamps] Re: AD Review of draft-ietf-lamps-cms-euf-cma-signeddata-02

Russ Housley <housley@vigilsec.com> Tue, 14 July 2026 18:18 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 6A538116BF65C for <spasm@mail2.ietf.org>; Tue, 14 Jul 2026 11:18:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784053131; bh=mLzRdo9Z68Y0e+2xVS/pUMXJa5HVbI4xBoqsb3gn9Ew=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=eozGZsXJdRwRgE9uHvuEe+KXKJDTfP6gS6UP5K4ee3md7/4ry4UDEY358qg0hb15h B5fZDubINroaEg9TYXu6L2VjvBkyyujdhritVVK+vGFXkgMySFeG1by4bL5Qtyx8al TDeQqmWmqUqIrtpvo1p3lZ//iVktStz8qzqXC/1U=
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 H-5V6GIZkClu for <spasm@mail2.ietf.org>; Tue, 14 Jul 2026 11:18:50 -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 E0AEA116BF652 for <spasm@ietf.org>; Tue, 14 Jul 2026 11:18:50 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id AEE531A18A1; Tue, 14 Jul 2026 14:18:50 -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 9B1BA1A1D3B; Tue, 14 Jul 2026 14:18:50 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <C818C2DE-ED7C-4CB0-A4D6-B1A56F105A55@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_DABE8248-5DD0-4842-8A4D-52122354394D"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.600.51.1.1\))
Date: Tue, 14 Jul 2026 14:18:40 -0400
In-Reply-To: <BN2P110MB110749A3E0A920D8B103933DDCF9A@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
To: Roman Danyliw <rdd@cert.org>
References: <BN2P110MB110749A3E0A920D8B103933DDCF9A@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
X-Mailer: Apple Mail (2.3864.600.51.1.1)
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=MP3MGYNPXQcfhm6+uFxirR9mbsNnqknTyaQj+hcnL3A=; b=EBeGaiOpya1lRNhjrTrmCqSDvyqn+PPin6LrjhvskCmWxkNQakUhfmCImWknQRjkjYumPNMfM6c/wCILRaD8pYdFTWTPn7/4DhZFZQkuFdNGoJE/bLbLpvlt+yZ7wDSU15Kfx/88FYO5gd8AJU9CXQX9Cg0ldAyLkZmwRuzTKHlPugKUpPXzMVqp0Jcv2frUGl+OmN3V9vSlNTLMs/8D1Sm98ou08FBulDwhY+zF8lGMwwQZyQnZgp/ezNhUowQfn2U0j1eZM7gKHuKdSs5Qw0Du4pIbUggOK3RRklRUSIqp5N/AOT0VNXyHMMriCMiA64bLRTAr8du0KYuNVEBJ7w==
X-Scanned-By: mailmunge 3.09
Message-ID-Hash: WQ7BK3QSIVA35ZPS6NGAGO7HHN764YPD
X-Message-ID-Hash: WQ7BK3QSIVA35ZPS6NGAGO7HHN764YPD
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: LAMPS <spasm@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [lamps] Re: AD Review of draft-ietf-lamps-cms-euf-cma-signeddata-02
List-Id: This is the mail list for the LAMPS Working Group <spasm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/JNB2luwYekABOH2u4B9th2FDCHA>
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>

Roman:


> To help balance the document load in coordination with the responsible AD for LAMPS (Deb Cooley), I will take over as responsible AD for draft-ietf-lamps-cms-euf-cma-signeddata. 

Thanks for helping.

> Thanks for this document.  My AD Review feedback is as follows:
>  
> ** WG Chairs and responsible AD for LAMPS: Your insight is needed.  This document appears to be outside of the charter for LAMPS.  It might fall into the remit of “This includes maintenance of protocols such as … Certificate Management over Cryptographic Message Syntax (CMS) (CMC)”.  However, all work in LAMPS appears to be restricted to Standards Track (“The LAMPS WG is now tackling these topics which will be published as Standards Track”) which precludes publication of a BCP, the classification of this document. 

While BCP document are not on the standards-track, thery require the same level of consensus, which is the way I took that statement.

Russ