Re: [pkix] Question about RFC 3125

Sean Turner <sean@sn3rd.com> Tue, 12 November 2019 16:03 UTC

Return-Path: <sean@sn3rd.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 261D8120837 for <pkix@ietfa.amsl.com>; Tue, 12 Nov 2019 08:03:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
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 utuyTg1mN67d for <pkix@ietfa.amsl.com>; Tue, 12 Nov 2019 08:03:44 -0800 (PST)
Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57EF412006F for <pkix@ietf.org>; Tue, 12 Nov 2019 08:03:44 -0800 (PST)
Received: by mail-qt1-x829.google.com with SMTP id 30so20271330qtz.12 for <pkix@ietf.org>; Tue, 12 Nov 2019 08:03:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=OGu0eULzFd8h/D4MQ7/A/psbUNKtaJHdzDcuY+7iukY=; b=b12AosOXC2OyubmjfG3fXuGq/xGisXYtLR9B9kOm2WZe1jt3tkU5MFHKgSZEoHe4Kf OyS3LwVPJvcBnX+vkunnxDqfB9ZNetDkvUegFv/oXuBKy4qCPtdch74URlw0oK7FFBxQ IyLgvH3tmLsvbfMKvzS0PnlhafyVoro3sTpC0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=OGu0eULzFd8h/D4MQ7/A/psbUNKtaJHdzDcuY+7iukY=; b=VxpbSoKJkohQszC+ZqQoh7pde7wgnNKqi8E7njgYeTeMCnKAQaG7zdmypdhxAQEf7G pt+9gOq7cWEtwwWUwgSZVk/PMOCnG3Q2Evow1+7ExFpcOCWRZnzdWiKzNrA8KlQOCvqa h+WPOIafijIW7VvEIKdpvnPppEuadfkdaXXPtIRMcgQUYN8iqjF2M1LvtHvKd95ei4ib S15tJ1repm5m6GQzwOURCTGeJ73KrAMFG3dm4IBOKebv8qvjvQ0t2PxK4csqfdVXXFMY ks/KwQ8cPXziIQk6yTRfCkcavS/wnbEJwrKLpR3S6iHRi3NIGo2dL+T24vzU0Kfx5rRA 2TiQ==
X-Gm-Message-State: APjAAAXHbj/4UEDabLxpqHS3m30PXWTAbNhAR2Whe+5tUGiirJnEFRRJ kjcHUl7bpgMtN3KsTb++o077RNjmsvY=
X-Google-Smtp-Source: APXvYqyaDYFNvcAXCyQtt49UvtSoKY1+2GktVkzED80ScIvHpK9l0P5rSOx8wwjKMHwom72WoB5KlQ==
X-Received: by 2002:ac8:38e3:: with SMTP id g32mr31781399qtc.103.1573574623377; Tue, 12 Nov 2019 08:03:43 -0800 (PST)
Received: from sn3rd.lan ([75.102.131.36]) by smtp.gmail.com with ESMTPSA id 40sm910168qtc.95.2019.11.12.08.03.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Nov 2019 08:03:42 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <86666A58-1AAA-4CEA-AADC-BDBCDFDD6519@vigilsec.com>
Date: Tue, 12 Nov 2019 11:03:41 -0500
Cc: IETF PKIX <pkix@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <FFAF24DE-7391-448D-93FF-D4EAACC62BB7@sn3rd.com>
References: <86666A58-1AAA-4CEA-AADC-BDBCDFDD6519@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/e1IoLgl33OJ8aVlEu437J8uv2r4>
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:03:46 -0000

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