RFC 10007 on Clarification to Processing Key Usage Values During Certificate Revocation List (CRL) Validation
rfc-editor@rfc-editor.org Tue, 30 June 2026 17:55 UTC
Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from celery-fbb6f4d95-pnwrp (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 71EC610B03878; Tue, 30 Jun 2026 10:55:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782842118; bh=emTfUIkA300Pp5UigxWiKG3swNiF9vRB6E3n4CJA51I=; h=Subject:From:To:Cc:Date; b=PG1UzfoIS48aRpgsbgujlVZwU5oE0nx4nGG6qlL50ZClAvs16MP+OwCHj1G2y89kd svg/wasOOZOy/BT9Lt24PvTv/L7oOAAsI8caTokxWqYVPkAqp/yO5o3phFXVVyO50T /CSz02o9Y9w19hX2kuZpExrs8YYcFq1epDr/XATc=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: RFC 10007 on Clarification to Processing Key Usage Values During Certificate Revocation List (CRL) Validation
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Date: Tue, 30 Jun 2026 17:55:18 -0000
message-id: <178284211811.12.17744258961374040612@rfc-editor.org>
Message-ID-Hash: CGBOEUXPY723QKRZVJUDQIK35HPKDXGQ
X-Message-ID-Hash: CGBOEUXPY723QKRZVJUDQIK35HPKDXGQ
X-MailFrom: rfc-editor@rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: drafts-update-ref@iana.org, spasm@ietf.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/IMjXppUuynM9EIerK_jsBz5weV8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
RFC 10007
Title: Clarification to Processing Key Usage Values
During Certificate Revocation List (CRL) Validation
Author: C. Bonnell,
T. Ito,
T. Okubo
Status: Proposed Standard
Stream: IETF
Date: June 2026
Mailbox: corey.bonnell@digicert.com,
tadahiko.ito.public@gmail.com,
tomofumi.okubo+ietf@gmail.com
Pages: 6
Updates: RFC 5280
I-D Tag: draft-ietf-lamps-keyusage-crl-validation-04
URL: https://www.rfc-editor.org/info/rfc10007
DOI: 10.17487/RFC10007
RFC 5280 defines the profile of X.509 certificates and Certificate
Revocation Lists (CRLs) for use in the Internet. Section 4.2.1.3 of
RFC 5280 requires CRL issuer certificates to contain the keyUsage
extension with the cRLSign bit asserted. However, the CRL validation
algorithm specified in Section 6.3 of RFC 5280 does not explicitly
include a corresponding check for the presence of the keyUsage
certificate extension. This document updates RFC 5280 to require
that check.
This document is a product of the Limited Additional Mechanisms for
PKIX and SMIME Working Group of the IETF.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and
suggestions for improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search/
For downloading RFCs, see https://www.rfc-editor.org/series/rfc-download/
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team