RFC 9919 on The Lightweight Online Certificate Status Protocol (OCSP) Profile for High-Volume Environments
rfc-editor@rfc-editor.org Wed, 15 July 2026 03:13 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-78f7859f6-lcn9z (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 2A66D116F2DD2; Tue, 14 Jul 2026 20:13:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784085194; bh=Q3yUobi39YF9a+cemdkZnGHl/h4Vq71dII3JuRCqXGg=; h=Subject:From:To:Cc:Date; b=rd+/OV//BY54wrcuUSCXxKfDj57OlNi3Yb4FZpnVcv6zbQRoulGhrSFpZD+UdlTKS aV/xA+jXARo1YSaOZ/eIt4HYQZANVUg+mqJCgpYxn3j7TRcotGvv6Yo7AbDOqWTmjt Kp/Hb/OF9KTDnDezcwqKDEqtrkwwe/NitxBgojSc=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: RFC 9919 on The Lightweight Online Certificate Status Protocol (OCSP) Profile for High-Volume Environments
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Date: Wed, 15 Jul 2026 03:13:14 -0000
message-id: <178408519405.18.11297734176030623425@rfc-editor.org>
Message-ID-Hash: X4VLE45CY33IV3EKMBFIDTX3KKNI2Q6B
X-Message-ID-Hash: X4VLE45CY33IV3EKMBFIDTX3KKNI2Q6B
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: spasm@ietf.org, drafts-update-ref@iana.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/7vD96YF_UbvTe9lvFPYMXurdMWA>
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 9919
Title: The Lightweight Online Certificate Status Protocol (OCSP) Profile for High-Volume Environments
Author: T. Ito,
C. Wilson,
C. Bonnell,
S. Turner
Status: Proposed Standard
Stream: IETF
Date: July 2026
Mailbox: tadahiko.ito.public@gmail.com,
clint.wilson@digicert.com,
corey.bonnell@turbolightsolutions.com,
sean@sn3rd.com
Pages: 32
Obsoletes: RFC 5019
I-D Tag: draft-ietf-lamps-rfc5019bis-12
URL: https://www.rfc-editor.org/info/rfc9919
DOI: 10.17487/RFC9919
This specification defines a profile of the Online Certificate Status
Protocol (OCSP) that addresses the scalability issues inherent when
using OCSP in large scale (high volume) Public Key Infrastructure
(PKI) environments and/or in PKI environments that require a
lightweight solution to minimize communication bandwidth and client-
side processing.
This specification obsoletes RFC 5019. The profile specified in RFC
5019 has been updated to allow and recommend the use of SHA-256 over
SHA-1.
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