[pkix] Question about RFC 3125

Russ Housley <housley@vigilsec.com> Tue, 12 November 2019 15:29 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EBEE12006E for <pkix@ietfa.amsl.com>; Tue, 12 Nov 2019 07:29:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ycv7dCgS4Oug for <pkix@ietfa.amsl.com>; Tue, 12 Nov 2019 07:29:06 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6952A12000F for <pkix@ietf.org>; Tue, 12 Nov 2019 07:29:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id CBB97300AEB for <pkix@ietf.org>; Tue, 12 Nov 2019 10:29:04 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id BP3qXRQ4G4Ba for <pkix@ietf.org>; Tue, 12 Nov 2019 10:29:03 -0500 (EST)
Received: from [5.5.33.39] (unknown [204.194.23.17]) by mail.smeinc.net (Postfix) with ESMTPSA id 8D960300A58 for <pkix@ietf.org>; Tue, 12 Nov 2019 10:29:03 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Message-Id: <86666A58-1AAA-4CEA-AADC-BDBCDFDD6519@vigilsec.com>
Date: Tue, 12 Nov 2019 10:29:03 -0500
To: IETF PKIX <pkix@ietf.org>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/5iXGGPwBygzigtcNsbi3C0wHNlI>
Subject: [pkix] Question about RFC 3125
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pkix/>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2019 15:29:08 -0000

Section 3.4 of RFC 3125 talks about Commitment Rules, and it specifies the following structure:

   CommitmentType ::= SEQUENCE {
        identifier                      CommitmentTypeIdentifier,
        fieldOfApplication      [0] FieldOfApplication OPTIONAL,
        semantics               [1] DirectoryString OPTIONAL }

However, CommitmentTypeIdentifier is never defined.  Is it an object identifier?

Can anyone point to a public signature policy that uses the SignaturePolicy defined in RFC 3125?

Russ