Re: [lamps] strugling with CSRAttrs

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 29 July 2022 19:05 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 5393EC1D1E44 for <spasm@ietfa.amsl.com>; Fri, 29 Jul 2022 12:05:42 -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_DNSWL_BLOCKED=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 ELUCy8YnRYtr for <spasm@ietfa.amsl.com>; Fri, 29 Jul 2022 12:05:38 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA2A1C157B47 for <spasm@ietf.org>; Fri, 29 Jul 2022 12:05:37 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [149.97.254.121]) by relay.sandelman.ca (Postfix) with ESMTPS id 78FB71F4A2; Fri, 29 Jul 2022 19:05:36 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id C6D981A05D0; Fri, 29 Jul 2022 14:45:08 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: David von Oheimb <it@von-Oheimb.de>, LAMPS WG <spasm@ietf.org>
In-reply-to: <ada963a796ca3fafb42a29751020ff4326fd2a1e.camel@von-Oheimb.de>
References: <12352.1657505901@localhost> <ada963a796ca3fafb42a29751020ff4326fd2a1e.camel@von-Oheimb.de>
Comments: In-reply-to David von Oheimb <it@von-Oheimb.de> message dated "Tue, 19 Jul 2022 20:58:37 +0200."
X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 29 Jul 2022 14:45:08 -0400
Message-ID: <563732.1659120308@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/OAwHUHf0t1P818PtbjZw8wFisRY>
Subject: Re: [lamps] strugling 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: Fri, 29 Jul 2022 19:05:42 -0000

>>    Attribute { ATTRIBUTE:IOSet } ::= SEQUENCE {
>>         extType  ATTRIBUTE.&id({IOSet}),
>>         extAttr  SET SIZE(1..MAX) OF ATTRIBUTE.&Type({IOSet}{@type})
>>    }
>
>Well, this definition is semantically identical to the original one.
>So better not rename the two fields of the Attribute structure, i.e., we
>should stick with 'type' and 'values',
>in particular since there may be attributes that are not X.509
>extensions.

I found it clearer, but if you object to this rename, then I'll go with your preference.

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