[rfc-dist] RFC 5055 on Server-Based Certificate Validation Protocol (SCVP)

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Wed Dec 12 15:04:39 PST 2007


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

        
        RFC 5055

        Title:      Server-Based Certificate Validation Protocol (SCVP) 
        Author:     T. Freeman, R. Housley,
                    A. Malpani, D. Cooper,
                    W. Polk
        Status:     Standards Track
        Date:       December 2007
        Mailbox:    trevorf at microsoft.com, 
                    housley at vigilsec.com, 
                    ambarish at yahoo.com,  david.cooper at nist.gov, 
                    wpolk at nist.gov
        Pages:      88
        Characters: 198764
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pkix-scvp-33.txt

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

The Server-Based Certificate Validation Protocol (SCVP) allows a
client to delegate certification path construction and certification
path validation to a server.  The path construction or validation
(e.g., making sure that none of the certificates in the path are
revoked) is performed according to a validation policy, which contains
one or more trust anchors.  It allows simplification of client
implementations and use of a set of predefined validation policies.  
[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

...




More information about the rfc-dist mailing list