[lamps] Re: I-D Action: draft-ietf-lamps-certdiscovery-04.txt

Russ Housley <housley@vigilsec.com> Fri, 30 October 2026 16:35 UTC

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 (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id C58D046 for <spasm@ietf.org>; Fri, 30 Oct 2026 16:35:36 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=vigilsec.com header.s=pair-202402141609 header.b=OUO1Jqoi; spf=pass (mx.ietf.org: domain of housley@vigilsec.com designates 66.39.134.11 as permitted sender) smtp.mailfrom=housley@vigilsec.com; dmarc=none
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id A29341605E9 for <spasm@ietf.org>; Fri, 30 Oct 2026 12:35:36 -0400 (EDT)
Received: from smtpclient.apple (pfs.iad.rg.net [198.180.150.6]) (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 84945127005 for <spasm@ietf.org>; Fri, 30 Oct 2026 12:35:35 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.700.51.1.1\))
Date: Fri, 30 Oct 2026 12:35:23 -0400
References: <179330683077.717056.1952181533983319494@dt-datatracker-7dc874ff8f-sl5zv>
To: IETF LAMPS <spasm@ietf.org>
In-Reply-To: <179330683077.717056.1952181533983319494@dt-datatracker-7dc874ff8f-sl5zv>
Message-Id: <019820D6-6820-4A8F-B72F-ED3AF15D1A14@vigilsec.com>
X-Mailer: Apple Mail (2.3864.700.51.1.1)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vigilsec.com; h=from:content-type:content-transfer-encoding:mime-version:subject:date:references:to:in-reply-to:message-id; s=pair-202402141609; bh=9UzWE+JQXOcNdN8v9BjqYs8btdNJuf53EXBXnIjvJo4=; b=OUO1Jqoia3TvrRYYoO4MtydrbQXz24IAWOZAgLkceI0wrjCeW6SRbvENJVOE/eeiYkZyTxMPqJgKEooxnX80GIPwx0jEdJdJDt+iRg23veZOJ0ajzuIWuRvLZ4XQvhUqnI8D8ug0ooUErZauJMmBn4+H/FEA35DWzsZMiQfBF9nzUU/XiFAZqWREcSzqxNBrP69lmzSN0uqw82nrmthlieGxptZCP9GZsVyy/+hcRydWnbTTwowI4KK+NcgFUdKbDgoywC648IHZDg56BUz73DO9iZFH5uQH6dWwEsCFjJOYledcHbvZ8fa1KWpwonMme7Tqcl7M7sk5Jgftyf71Ww==
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
X-Spamd-Bar: ---------------------------
Message-ID-Hash: 5ZAMNMEFWYGJNWXO6PLWHULMFSQ2SUM4
X-Message-ID-Hash: 5ZAMNMEFWYGJNWXO6PLWHULMFSQ2SUM4
X-MailFrom: housley@vigilsec.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-spasm.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [lamps] Re: I-D Action: draft-ietf-lamps-certdiscovery-04.txt
List-Id: This is the mail list for the LAMPS Working Group <spasm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/Gf4E24WwQ2DLjftoj-7yIp7uIYw>
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>

I cannot get the ASN.1 to compile because the use of AlgorithmIdentifier does not align with RFC 5911.

For example, you might define:

    SignatureAlg ::= AlgorithmIdentifier{ SIGNATURE-ALGORITHM, ... }

Russ

> On Oct 29, 2026, at 4:47 PM, internet-drafts@ietf.org wrote:
> 
> Internet-Draft draft-ietf-lamps-certdiscovery-04.txt is now available. It is a
> work item of the Limited Additional Mechanisms for PKIX and SMIME (LAMPS) WG
> of the IETF.
> 
>   Title:   A Mechanism for X.509 Certificate Discovery
>   Authors: Tomofumi Okubo
>            Corey Bonnell
>            John Gray
>            Mike Ounsworth
>            Joe Mandel
>   Name:    draft-ietf-lamps-certdiscovery-04.txt
>   Pages:   13
>   Dates:   2026-10-29
> 
> Abstract:
> 
>   This document specifies a method to discover a referenced X.509
>   certificate associated with the current X.509 certificate.  This
>   enables efficient multi-certificate or fallback certificate handling
>   in protocols.  The objective is threefold: to enhance cryptographic
>   agility, improve operational availability, and accommodate multi-key/
>   certificate usage.  The proposed method aims to maximize
>   compatibility with existing systems and is designed to be legacy-
>   friendly, making it suitable for environments with a mix of legacy
>   and new implementations.  It includes mechanisms to provide a URI
>   from which the referenced X.509 certificate can be retrieved as well
>   as information about the target certificate's signature and public
>   key algorithm, empowering relying parties to make informed decisions
>   on whether to retrieve the Referenced Certificate, and a certificate
>   hash to ensure that the correct certificate was retrieved.
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-lamps-certdiscovery/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-lamps-certdiscovery-04.html
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-lamps-certdiscovery-04
> 
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
> 
> 
> _______________________________________________
> Spasm mailing list -- spasm@ietf.org
> To unsubscribe send an email to spasm-leave@ietf.org