Re: [pkix] Question about RFC 3125

Stefan Santesson <stefan@aaa-sec.com> Tue, 12 November 2019 16:15 UTC

Return-Path: <stefan@aaa-sec.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 48BB712009C for <pkix@ietfa.amsl.com>; Tue, 12 Nov 2019 08:15:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 ZGIVisij6j70 for <pkix@ietfa.amsl.com>; Tue, 12 Nov 2019 08:15:06 -0800 (PST)
Received: from smtp2.outgoing.loopia.se (smtp2.outgoing.loopia.se [93.188.3.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCBD5120098 for <pkix@ietf.org>; Tue, 12 Nov 2019 08:15:05 -0800 (PST)
Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id C51D32E4D01E for <pkix@ietf.org>; Tue, 12 Nov 2019 17:15:02 +0100 (CET)
Received: from s630.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id A69902E27E8A; Tue, 12 Nov 2019 17:15:02 +0100 (CET)
Received: from s475.loopia.se (unknown [172.22.191.5]) by s630.loopia.se (Postfix) with ESMTP id 965C913ABD80; Tue, 12 Nov 2019 17:15:02 +0100 (CET)
X-Virus-Scanned: amavisd-new at amavis.loopia.se
Received: from s499.loopia.se ([172.22.191.5]) by s475.loopia.se (s475.loopia.se [172.22.190.15]) (amavisd-new, port 10024) with LMTP id IwiNx3cNLwGI; Tue, 12 Nov 2019 17:15:02 +0100 (CET)
X-Loopia-Auth: user
X-Loopia-User: mailstore2@aaa-sec.com
X-Loopia-Originating-IP: 85.235.7.89
Received: from [192.168.2.38] (gw.aaa-sec.ideon.se [85.235.7.89]) (Authenticated sender: mailstore2@aaa-sec.com) by s499.loopia.se (Postfix) with ESMTPSA id 0A4A81CDAE33; Tue, 12 Nov 2019 17:15:01 +0100 (CET)
User-Agent: Microsoft-MacOutlook/10.1e.0.191013
Date: Tue, 12 Nov 2019 17:15:01 +0100
From: Stefan Santesson <stefan@aaa-sec.com>
To: Sean Turner <sean@sn3rd.com>, Russ Housley <housley@vigilsec.com>
CC: IETF PKIX <pkix@ietf.org>
Message-ID: <F199D98E-1218-4FB6-A027-74D5C4386538@aaa-sec.com>
Thread-Topic: [pkix] Question about RFC 3125
References: <86666A58-1AAA-4CEA-AADC-BDBCDFDD6519@vigilsec.com> <FFAF24DE-7391-448D-93FF-D4EAACC62BB7@sn3rd.com>
In-Reply-To: <FFAF24DE-7391-448D-93FF-D4EAACC62BB7@sn3rd.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/TiC-F9T7rXBdCH7dfRn5nyXqG6o>
Subject: Re: [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 16:15:08 -0000

It's defined as OID in the referenced document ETSI TS101733
https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.02.01_60/ts_101733v020201p.pdf

It's also defined in the new version that obsoletes 101733 (ETSI EN 319 122-1)
https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.01.01_60/en_31912201v010101p.pdf


Stefan Santesson 

´╗┐On 2019-11-12, 17:03, "pkix on behalf of Sean Turner" <pkix-bounces@ietf.org on behalf of sean@sn3rd.com> wrote:

    I mean it has to be an OID - right?
    
    spt
    
    > On Nov 12, 2019, at 10:29, Russ Housley <housley@vigilsec.com> wrote:
    > 
    > 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
    > 
    > _______________________________________________
    > pkix mailing list
    > pkix@ietf.org
    > https://www.ietf.org/mailman/listinfo/pkix
    
    _______________________________________________
    pkix mailing list
    pkix@ietf.org
    https://www.ietf.org/mailman/listinfo/pkix