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:    [email protected],
                    [email protected],
                    [email protected],
                    [email protected]
        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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team

_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to