IETF Logo Mail Archive

[lamps] Re: Mohamed Boucadair's Discuss on draft-ietf-lamps-rfc7030-csrattrs-20: (with DISCUSS and COMMENT)

Russ Housley <housley@vigilsec.com> Tue, 06 May 2025 13:39 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 8CA90255E3D8; Tue, 6 May 2025 06:39:22 -0700 (PDT)
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_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_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 Z2nGtHFCjn9B; Tue, 6 May 2025 06:39:22 -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 0A255255E3CE; Tue, 6 May 2025 06:39:22 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id E53F61A0FA1; Tue, 6 May 2025 09:39:21 -0400 (EDT)
Received: from smtpclient.apple (unknown [96.241.2.243]) (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 C9CD51A26BF; Tue, 6 May 2025 09:39:21 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <2D344072-E9A3-4CFB-9E8C-A5E73301F359@vigilsec.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_ED09DEAD-CA8A-478D-8989-62BD961B5171"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.500.181.1.5\))
Date: Tue, 06 May 2025 09:39:11 -0400
In-Reply-To: <174651635815.664864.12648748464955509992@dt-datatracker-58d4498dbd-6gzjf>
To: Med Boucadair <mohamed.boucadair@orange.com>
References: <174651635815.664864.12648748464955509992@dt-datatracker-58d4498dbd-6gzjf>
X-Mailer: Apple Mail (2.3826.500.181.1.5)
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=s6k5lFtaqEtiB+chaNSR9xniyCBTh80Nt+Fj1H5Onwc=; b=smwuYboKNrgn29rZBMiDr+KCmIJJY5aNmrK199Ze8SvYc0WZLiI/gqjEq0zjjYpsglnsUxjB5MKZnxui+F7bBbTZ7X4j1+alD4XD6EXMtZi7ANzqY/k8oTAmM+FBH/BFafiXO55Z3Rjj87V0aQlyQugeZ/aOQv+kb8dtLZRmInjn2CCZBL2twn2dsdTYQvOpWwsXtmB9rPdo7NIStJObfI3Q1voXE+XWMIUfucGaBC29PeW6CyzYcXmbGELbHU9VNd1F5TW+NjkE+ZvLi0+q9T3SroTGpPZ0qLCd6as0YjpuQflQ7r09HAeb70EGT2CET2ocCsXd3HgC07uBK1RaqA==
X-Scanned-By: mailmunge 3.09 on 66.39.134.11
Message-ID-Hash: VPHQJGPXGXTJG5KHY6YDEGH7UACKUPFO
X-Message-ID-Hash: VPHQJGPXGXTJG5KHY6YDEGH7UACKUPFO
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: IESG <iesg@ietf.org>, draft-ietf-lamps-rfc7030-csrattrs@ietf.org, lamps-chairs@ietf.org, spasm@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [lamps] Re: Mohamed Boucadair's Discuss on draft-ietf-lamps-rfc7030-csrattrs-20: (with DISCUSS and COMMENT)
List-Id: This is the mail list for the LAMPS Working Group <spasm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/mJDMVA-TEk-KmfD2-OsLGTwL5d4>
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>


> On May 6, 2025, at 3:25 AM, Mohamed Boucadair via Datatracker <noreply@ietf.org> wrote:
> 
> 
> # DISCUSS
> 
> ## Conflict between registered IANA value vs ASN Module
> 
> Section 7 has the following:
> 
>   *  One (TBD2) from the SMI Security for S/MIME Attributes
>      (1.2.840.113549.1.9.16.2) registry for the Certification Request
>      Information Template (id-aa-csrinfo) attribute; see Appendix A
> 
> while Appendix A has:
> 
>   id-aa-certificationRequestInfoTemplate OBJECT IDENTIFIER ::=
>     { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
>       smime(16) aa(2) csrinfo(TBD2)
> 
> Please check.
> 
> As I’m there, please fix the following:
> 
> OLD: IANA is asked to allocate two new Object Identifiers
> 
> NEW: IANA is asked to allocate three new Object Identifiers

You are correct, the IANA consideration should read as follows:

   IANA is asked to allocate three new Object Identifiers:

   *  One (TBD1) from the SMI Security for S/MIME Module Identifier
      (1.2.840.113549.1.9.16.0) registry for the ASN.1 module: id-mod-
      critemplate; see Appendix A.

   *  One (TBD2) from the SMI Security for S/MIME Attributes
      (1.2.840.113549.1.9.16.2) registry for the Certification Request
      Information Template (id-aa-certificationRequestInfoTemplate)
      attribute; see Appendix A.

   *  One (TBD3) SMI Security for S/MIME Attributes
      (1.2.840.113549.1.9.16.2) registry for the extension request
      template (id-aa-extensionReqTemplate) attribute; see Appendix A.

Russ

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