[lamps] Last Call: <draft-ietf-lamps-rfc5019bis-05.txt> (Updates to Lightweight OCSP Profile for High Volume Environments) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Sat, 09 March 2024 00:34 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
CC: draft-ietf-lamps-rfc5019bis@ietf.org, housley@vigilsec.com, lamps-chairs@ietf.org, rdd@cert.org, spasm@ietf.org
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <170994446524.48931.13618986531654098738@ietfa.amsl.com>
Date: Fri, 08 Mar 2024 16:34:25 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/QMiueGySHrc5Jaie9k2ONKDmmhA>
Subject: [lamps] Last Call: <draft-ietf-lamps-rfc5019bis-05.txt> (Updates to Lightweight OCSP Profile for High Volume Environments) to Proposed Standard

The IESG has received a request from the Limited Additional Mechanisms for
PKIX and SMIME WG (lamps) to consider the following document: - 'Updates to
Lightweight OCSP Profile for High Volume Environments'
<draft-ietf-lamps-rfc5019bis-05.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2024-03-29. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract

RFC 5019 defines a lightweight profile for OCSP that makes the
protocol more suitable for use in high-volume environments. The
lightweight profile specifies the mandatory use of SHA-1 when
calculating the values of several fields in OCSP requests and
responses. In recent years, weaknesses have been demonstrated with
the SHA-1 algorithm. As a result, SHA-1 is increasingly falling out
of use even for non-security relevant use cases. This document
obsoletes the lightweight profile as specified in RFC 5019 to instead
recommend the use of SHA-256 where SHA-1 was previously required. An
RFC 5019-compliant OCSP client is still able to use SHA-1, but the
use of SHA-1 may become obsolete in the future.

The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-lamps-rfc5019bis/

No IPR declarations have been submitted directly on this I-D.

The document contains these normative downward references.
See RFC 3967 for additional information:
draft-ietf-tls-rfc8446bis: The Transport Layer Security (TLS) Protocol Version 1.3 (None - Internet Engineering Task Force (IETF))

[lamps] Last Call: <draft-ietf-lamps-rfc5019bis-0… The IESG