RFC 9608 on No Revocation Available for X.509 Public Key Certificates

A new Request for Comments is now available in online RFC libraries.

        RFC 9608

        Title:      No Revocation Available for X.509 
                    Public Key Certificates 
        Author:     R. Housley,
                    T. Okubo,
                    J. Mandel
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2024
        Mailbox:    housley@vigilsec.com,
                    tomofumi.okubo+ietf@gmail.com,
                    joe@akayla.com
        Pages:      10
        Updates:    RFC 5280

        I-D Tag:    draft-ietf-lamps-norevavail-04.txt

        URL:        https://www.rfc-editor.org/info/rfc9608

        DOI:        10.17487/RFC9608

X.509v3 public key certificates are profiled in RFC 5280. 
Short-lived certificates are seeing greater use in the Internet.  The
Certification Authority (CA) that issues these short-lived
certificates do not publish revocation information because the
certificate lifespan that is shorter than the time needed to detect,
report, and distribute revocation information.  Some long-lived
X.509v3 public key certificates never expire, and they are never
revoked.  This specification defines the noRevAvail certificate
extension so that a relying party can readily determine that the CA
does not publish revocation information for the certificate, and it
updates the certification path validation algorithm defined in RFC
5280 so that revocation checking is skipped when the noRevAvail
certificate extension is present.

This document is a product of the Limited Additional Mechanisms for PKIX and SMIME Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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/retrieve/bulk

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
Association Management Solutions, LLC