Server-Based Certificate Validation Protocol (SCVP)
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: IETF-Announce <firstname.lastname@example.org> Cc: Internet Architecture Board <email@example.com>, RFC Editor <firstname.lastname@example.org>, pkix mailing list <email@example.com>, pkix chair <firstname.lastname@example.org> Subject: Protocol Action: 'Server-based Certificate Validation Protocol (SCVP)' to Proposed Standard The IESG has approved the following document: - 'Server-based Certificate Validation Protocol (SCVP) ' <draft-ietf-pkix-scvp-34.txt> as a Proposed Standard This document is the product of the Public-Key Infrastructure (X.509) Working Group. The IESG contact persons are Sam Hartman and Tim Polk. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pkix-scvp-34.txt
Technical Summary SCVP allows a client to delegate certificate path construction and certificate 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. Working Group Summary The working group expressed consensus to advance the draft to Proposed Standard. Two participants raised concerns that this protocol did not meet all the requirements of RFC 3379 and introduced significant new features. The working group investigated this claim and concluded that after minor revisions this document does meet the requirements and does not introduce significant new features. Protocol Quality This document has been reviewed by members of the email@example.com mailing list and by the working group chairs. The protocol seems reasonable. This has been reviewed by Sam Hartman for the IESG.