[pkix] [Errata Verified] RFC6818 (9264)

rfc-editor@rfc-editor.org Mon, 02 November 2026 22:24 UTC

Received: by mx.ietf.org (Postfix) id A9F3946; Mon, 02 Nov 2026 22:24:11 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rfc-editor.org; s=mail; t=1793658252; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=ObThcvXJGdC2yGOCs0GeYp5+PRJMPOnHTAty0Q6jCKk=; b=dMLNLLj935S6fzXACdKluyn7m4rMcZqsG3ktnw2sN3nAUErS115T/DkqJQenuExndLyned FD9vp0plonKrs+GMeMuCxQ8/dquGb0L5aH8Jm4m9UZ0VYPmL/oB7cSxBD1wCBD4zQ5qGj2 fz7aJy+gySJ2hQTH5ZeTjN00cQzn4v8=
Authentication-Results: ORIGINATING; auth=pass smtp.auth=mail2@ietf.org smtp.mailfrom=rfc-editor@rfc-editor.org
Received: from errata-celery-6f84c7996-wb2x7 (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 73C4613B72C0F; Mon, 2 Nov 2026 14:24:11 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: rfc-editor@rfc-editor.org
To: hi@arxo.io, peter@akayla.com
Date: Mon, 02 Nov 2026 22:24:11 -0000
message-id: <179365825137.11.3374012671834140149@rfc-editor.org>
Message-ID-Hash: PRORWOG2IAGD6MGLG3SOUZBGQPRXVNYV
X-Message-ID-Hash: PRORWOG2IAGD6MGLG3SOUZBGQPRXVNYV
X-MailFrom: rfc-editor@rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-pkix.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: iana@iana.org, pkix@ietf.org, iesg@ietf.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [pkix] [Errata Verified] RFC6818 (9264)
List-Id: PKIX Working Group <pkix.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/Hc-wqBboD_aAsPG3jTDtNUBk-rw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pkix>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Owner: <mailto:pkix-owner@ietf.org>
List-Post: <mailto:pkix@ietf.org>
List-Subscribe: <mailto:pkix-join@ietf.org>
List-Unsubscribe: <mailto:pkix-leave@ietf.org>

The following errata report has been verified for RFC6818,
"Updates to the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"

--------------------------------------
You may review the report below and at:
https://errata.rfc-editor.org/eid9264/

--------------------------------------

Status: Verified
Type: Editorial
Reported by: Rifat Jumagulov <hi@arxo.io>
Date Reported: Nov. 1, 2026, 1:26 p.m.
Verified by: Madison Church (RFC Production Center)

Section 6 says:

Original Text
-------------
| One-way hash functions are commonly used to generate key identifier
| values (AKI and SKI), e.g., as described in Sections 4.1.1 and 4.1.2.
| However, none of the security properties of such functions are
| required for this context.

Corrected Text
--------------
| One-way hash functions are commonly used to generate key identifier
| values (AKI and SKI), e.g., as described in Sections 4.2.1.1 and
| 4.2.1.2.  However, none of the security properties of such functions
| are required for this context.

Notes
-----
This paragraph is added to the Security Considerations of RFC 5280, so "Sections 4.1.1 and 4.1.2" point into RFC 5280. There, Section 4.1.1 is "Certificate Fields" and Section 4.1.2 is "TBSCertificate"; neither describes key identifiers. The authority and subject key identifiers are Sections 4.2.1.1 and 4.2.1.2, and the SHA-1 methods for generating them are given in Section 4.2.1.2.

AI models helped review the text and build small test models; Arxo ran the checks, and I take responsibility for the reports.

--------------------------------------
RFC6818 (draft-ietf-pkix-rfc5280-clarifications)
--------------------------------------
Title               : Updates to the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
Publication Date    : January 2013
Author(s)           : P. Yee
Category            : Proposed Standard
Source              : pkix (sec)
Stream              : IETF