RFC 5019 on The Lightweight Online Certificate Status Protocol (OCSP) Profile for High-Volume Environments

[rfc-editor at rfc-editor.org]

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

        
        RFC 5019

        Title:      The Lightweight Online Certificate Status 
                    Protocol (OCSP) Profile for High-Volume Environments 
        Author:     A. Deacon, R. Hurst
        Status:     Standards Track
        Date:       September 2007
        Mailbox:    alex at verisign.com, 
                    rmh at microsoft.com
        Pages:      22
        Characters: 46371
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pkix-lightweight-ocsp-profile-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5019.txt

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.  [STANDARDS TRACK]

This document is a product of the Public-Key Infrastructure (X.509)
Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 Internet
 Official Protocol Standards (STD 1) for the standardization state and
 status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce