IETF Logo Mail Archive

Re: [lamps] Fixed the RFC 8994 / ACP Subject Alternative Name example - Re: struggling with CSRAttrs

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 28 September 2022 15:55 UTC

Return-Path: <mcr@sandelman.ca>
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 CF15FC1524DC for <spasm@ietfa.amsl.com>; Wed, 28 Sep 2022 08:55:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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 07gJ4um_zDzt for <spasm@ietfa.amsl.com>; Wed, 28 Sep 2022 08:55:44 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (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 D12E3C152563 for <spasm@ietf.org>; Wed, 28 Sep 2022 08:55:44 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [46.183.103.8]) by relay.sandelman.ca (Postfix) with ESMTPS id 689001F455; Wed, 28 Sep 2022 15:55:40 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 7B1581A0749; Wed, 28 Sep 2022 17:55:11 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: David von Oheimb <David.von.Oheimb@siemens.com>, Corey Bonnell <Corey.Bonnell@digicert.com>, LAMPS WG <spasm@ietf.org>
In-reply-to: <19f4388a-49e1-d14e-2463-e9f0e181c2ea@siemens.com>
References: <12352.1657505901@localhost> <ada963a796ca3fafb42a29751020ff4326fd2a1e.camel@von-Oheimb.de> <563732.1659120308@dooku> <36c409c2-ab92-4ec2-6f1e-235652a243d9@siemens.com> <3758.1659557693@localhost> <399c3a1e-ee28-cc85-6e6a-cee210e70753@siemens.com> <DM6PR14MB2186188B8CFA66967F52A081929F9@DM6PR14MB2186.namprd14.prod.outlook.com> <19f4388a-49e1-d14e-2463-e9f0e181c2ea@siemens.com>
Comments: In-reply-to David von Oheimb <David.von.Oheimb@siemens.com> message dated "Fri, 05 Aug 2022 11:29:41 +0200."
X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 27.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 28 Sep 2022 17:55:11 +0200
Message-ID: <127758.1664380511@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/Mwy4M0p_C7uLaiV1d_lv2PgDNwI>
Subject: Re: [lamps] Fixed the RFC 8994 / ACP Subject Alternative Name example - Re: struggling with CSRAttrs
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <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: Wed, 28 Sep 2022 15:55:46 -0000

David von Oheimb <David.von.Oheimb@siemens.com> wrote:
    > Side note: Now I wonder why the rather uncommon and cumbersome
    > otherName choice has been taken for ACP.  Looks like implementation
    > support for otherNames is not the best.  Since an IA5String should be
    > used for ACP that looks like an email address, one might have chosen
    > instead the simpler and well supported GeneralName choice 'rfc822name':

Well, Toerless argued for years to use rfc822Name, and we had running code,
but there were objections to this, so at the last minute RFC8994 moved to
otherName.  The running code is still catching up.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email