IETF Logo Mail Archive

Re: [lamps] CSRattr: is new OID in correct arc?

Russ Housley <housley@vigilsec.com> Mon, 06 November 2023 09:04 UTC

Return-Path: <housley@vigilsec.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 1BAB7C1705EE for <spasm@ietfa.amsl.com>; Mon, 6 Nov 2023 01:04:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 q7wpVItqSlnO for <spasm@ietfa.amsl.com>; Mon, 6 Nov 2023 01:04:14 -0800 (PST)
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 RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7CB1C151066 for <spasm@ietf.org>; Mon, 6 Nov 2023 01:04:13 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id D37758627B; Mon, 6 Nov 2023 04:04:12 -0500 (EST)
Received: from smtpclient.apple (dhcp-8299.meeting.ietf.org [31.133.130.153]) (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 6B147865B0; Mon, 6 Nov 2023 04:04:12 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_0F6E4526-0D2D-4667-B776-D382A0BE189F"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <3512329.1699260203@dyas>
Date: Mon, 06 Nov 2023 04:04:00 -0500
Cc: LAMPS <spasm@ietf.org>
Message-Id: <52ECECD7-AC7E-4827-BE1A-B563DAB85021@vigilsec.com>
References: <3512329.1699260203@dyas>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3731.700.6)
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/HOsessPXGk_Je6cJOCR1eAvA_q0>
Subject: Re: [lamps] CSRattr: is new OID in correct arc?
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: Mon, 06 Nov 2023 09:04:16 -0000


> On Nov 6, 2023, at 3:43 AM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> In draft-ietf-lamps-rfc7030-csrattrs-07 We are asking for a new OID in:
> 
>    id-aa-certificationRequestInfoTemplate OBJECT IDENTIFIER ::= {
>        iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
>        smime(16) aa(2) TBD }
> 
> Sean's similar, but not exactly equivalent RFC8295, Appendix B used:
> 
>     pkcs-9-at-pkcs7PDU OBJECT IDENTIFIER ::= {
>       iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
>       pkcs-9-at(25) 5
>       }
> 
> And we wondered why smime, and if we should be using an OID from another arc?

There are lots of attributes in { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9) smime(16) aa(2) }.  They are mostly used in signed attributes or authenticated attributes.  I am fine with more attributes here or creating an new arc under the pkic arc for CSR attributes.

Russ

v2.23.0 | Report a Bug | By Email