Re: [pkix] [Editorial Errata Reported] RFC3739 (7801)
Russ Housley <housley@vigilsec.com> Wed, 07 February 2024 20:11 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 A00EDC14CF0D for <pkix@ietfa.amsl.com>; Wed, 7 Feb 2024 12:11:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, PDS_OTHER_BAD_TLD=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 ITGpKpRfQ3kq for <pkix@ietfa.amsl.com>; Wed, 7 Feb 2024 12:11:30 -0800 (PST)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (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 55140C14CEED for <pkix@ietf.org>; Wed, 7 Feb 2024 12:11:30 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id B24C514314A; Wed, 7 Feb 2024 15:11:29 -0500 (EST)
Received: from smtpclient.apple (unknown [96.241.2.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 9CA27142457; Wed, 7 Feb 2024 15:11:29 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <SN7PR14MB64924C35409F81205E128EAA83452@SN7PR14MB6492.namprd14.prod.outlook.com>
Date: Wed, 07 Feb 2024 15:11:19 -0500
Cc: IETF PKIX <pkix@ietf.org>, Stefan Santesson <stefan@aaa-sec.com>, Magnus Nystrom <magnusn@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <98765409-F78B-4D81-9328-5DBB989F7C6A@vigilsec.com>
References: <20240207191418.DD5A618FA484@rfcpa.amsl.com> <SN7PR14MB64924C35409F81205E128EAA83452@SN7PR14MB6492.namprd14.prod.outlook.com>
To: RFC Editor <rfc-editor@rfc-editor.org>
X-Mailer: Apple Mail (2.3731.700.6)
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/zK0qsQO5V8fGMW8sEoqsHEXtMbU>
Subject: Re: [pkix] [Editorial Errata Reported] RFC3739 (7801)
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 07 Feb 2024 20:11:34 -0000
The same typo appears earlier in the same paragraph: Original: If a value of type SemanticsInformation is present in a QCStatement where the statementID component is set to id-qcs-pkix-QCSyntax-v1 or id-qcs-pkix-QCSyntax-v2, then at least one of the semanticsIdentifier or nameRegistrationAuthorities fields must be present, as indicated. Note that the statementInfo component need not be present in a QCStatement value even if the statementID component is set to id- qcs-pkix-QCSyntax-v1 or id-qcs-pkix-QCSyntax-v2. Corrected: If a value of type SemanticsInformation is present in a QCStatement where the statementId component is set to id-qcs-pkix-QCSyntax-v1 or id-qcs-pkix-QCSyntax-v2, then at least one of the semanticsIdentifier or nameRegistrationAuthorities fields must be present, as indicated. Note that the statementInfo component need not be present in a QCStatement value even if the statementId component is set to id- qcs-pkix-QCSyntax-v1 or id-qcs-pkix-QCSyntax-v2. Russ > On Feb 7, 2024, at 2:58 PM, Tim Hollebeek <tim.hollebeek=40digicert.com@dmarc.ietf.org> wrote: > > I've reviewed this and Corey is correct. The errata should be confirmed. > > -Tim > >> -----Original Message----- >> From: pkix <pkix-bounces@ietf.org> On Behalf Of RFC Errata System >> Sent: Wednesday, February 7, 2024 2:14 PM >> To: rfc-editor@rfc-editor.org >> Cc: pkix@ietf.org; wpolk@nist.gov; stefans@microsoft.com; >> magnus@rsasecurity.com >> Subject: [pkix] [Editorial Errata Reported] RFC3739 (7801) >> >> The following errata report has been submitted for RFC3739, "Internet > X.509 >> Public Key Infrastructure: Qualified Certificates Profile". >> >> -------------------------------------- >> You may review the report below and at: >> https://url.avanan.click/v2/___https://www.rfc- >> editor.org/errata/eid7801___.YXAzOmRpZ2ljZXJ0OmE6bzpmOWVjYTZlMmZk >> ZGExZmNlOTBkODM1MDgxNTNiZjZmNTo2OjE3Nzg6MjBiODMwZjU4YmVlY2 >> NmNmI2MWU3YThmY2NiODc3NDRlZTgzNjQ4OWJjMDA0NmMwMWY3OD >> M5YTMzMjFhY2ZjYjpwOkY >> >> -------------------------------------- >> Type: Editorial >> Reported by: Corey Bonnell <corey.bonnell@digicert.com> >> >> Section: 3.2.6.1 >> >> Original Text >> ------------- >> Note that the statementInfo component need not be present in a >> QCStatement value even if the statementID component is set to id- >> qcs-pkix-QCSyntax-v1 or id-qcs-pkix-QCSyntax-v2. >> >> Corrected Text >> -------------- >> Note that the statementInfo component need not be present in a >> QCStatement value even if the statementId component is set to id- >> qcs-pkix-QCSyntax-v1 or id-qcs-pkix-QCSyntax-v2. >> >> Notes >> ----- >> The name of the statement ID component per the ASN.1 definition is >> "statementId", not "statementID". >> >> Instructions: >> ------------- >> This erratum is currently posted as "Reported". (If it is spam, it will be > removed >> shortly by the RFC Production Center.) Please use "Reply All" to discuss >> whether it should be verified or rejected. When a decision is reached, the >> verifying party will log in to change the status and edit the report, if > necessary. >> >> -------------------------------------- >> RFC3739 (draft-ietf-pkix-sonof3039-06) >> -------------------------------------- >> Title : Internet X.509 Public Key Infrastructure: Qualified > Certificates >> Profile >> Publication Date : March 2004 >> Author(s) : S. Santesson, M. Nystrom, T. Polk >> Category : PROPOSED STANDARD >> Source : Public-Key Infrastructure (X.509) >> Area : Security >> Stream : IETF >> Verifying Party : IESG >> >> _______________________________________________ >> pkix mailing list >> pkix@ietf.org >> > https://url.avanan.click/v2/___https://www.ietf.org/mailman/listinfo/pkix__ >> _.YXAzOmRpZ2ljZXJ0OmE6bzpmOWVjYTZlMmZkZGExZmNlOTBkODM1MDgx >> NTNiZjZmNTo2OjA3M2I6NGVkNWViMDJkYzkxZWM4NjczYjFmOWZkMjE4YjZ >> kMzQ5ODg1Y2ViYTMyZDZmYjNlNThiZjBiM2JjNGRhMzA4NjpwOkY > _______________________________________________ > pkix mailing list > pkix@ietf.org > https://www.ietf.org/mailman/listinfo/pkix
- [pkix] [Editorial Errata Reported] RFC3739 (7801) RFC Errata System
- Re: [pkix] [Editorial Errata Reported] RFC3739 (7… Tim Hollebeek
- Re: [pkix] [Editorial Errata Reported] RFC3739 (7… Russ Housley