RFC 5276 on Using the Server-Based Certificate Validation Protocol (SCVP) to Convey Long-Term Evidence Records
rfc-editor@rfc-editor.org Wed, 13 August 2008 16:47 UTC
Return-Path: <owner-ietf-ltans@mail.imc.org>
X-Original-To: ietfarch-ltans-archive-ba2WohFa@core3.amsl.com
Delivered-To: ietfarch-ltans-archive-ba2WohFa@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E0F783A6B57 for <ietfarch-ltans-archive-ba2WohFa@core3.amsl.com>; Wed, 13 Aug 2008 09:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.878
X-Spam-Level:
X-Spam-Status: No, score=-1.878 tagged_above=-999 required=5 tests=[AWL=-0.432, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_93=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PNIsXGD7fMTr for <ietfarch-ltans-archive-ba2WohFa@core3.amsl.com>; Wed, 13 Aug 2008 09:47:04 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 008843A6B05 for <ltans-archive-ba2WohFa@ietf.org>; Wed, 13 Aug 2008 09:47:03 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m7DGbMVH058170 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Aug 2008 09:37:22 -0700 (MST) (envelope-from owner-ietf-ltans@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m7DGbM9L058169; Wed, 13 Aug 2008 09:37:22 -0700 (MST) (envelope-from owner-ietf-ltans@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m7DGbLe8058163 for <ietf-ltans@imc.org>; Wed, 13 Aug 2008 09:37:22 -0700 (MST) (envelope-from rfc-editor@rfc-editor.org)
Received: by bosco.isi.edu (Postfix, from userid 70) id 71F7414DCBD; Wed, 13 Aug 2008 09:37:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5276 on Using the Server-Based Certificate Validation Protocol (SCVP) to Convey Long-Term Evidence Records
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, ietf-ltans@imc.org
Message-Id: <20080813163721.71F7414DCBD@bosco.isi.edu>
Date: Wed, 13 Aug 2008 09:37:21 -0700
Sender: owner-ietf-ltans@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-ltans/mail-archive/>
List-Unsubscribe: <mailto:ietf-ltans-request@imc.org?body=unsubscribe>
List-ID: <ietf-ltans.imc.org>
A new Request for Comments is now available in online RFC libraries. RFC 5276 Title: Using the Server-Based Certificate Validation Protocol (SCVP) to Convey Long-Term Evidence Records Author: C. Wallace Status: Standards Track Date: August 2008 Mailbox: cwallace@cygnacom.com Pages: 13 Characters: 27422 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ltans-ers-scvp-07.txt URL: http://www.rfc-editor.org/rfc/rfc5276.txt The Server-based Certificate Validation Protocol (SCVP) defines an extensible means of delegating the development and validation of certification paths to a server. It can be used to support the development and validation of certification paths well after the expiration of the certificates in the path by specifying a time of interest in the past. The Evidence Record Syntax (ERS) defines structures, called evidence records, to support the non-repudiation of the existence of data. Evidence records can be used to preserve materials that comprise a certification path such that trust in the certificates can be established after the expiration of the certificates in the path and after the cryptographic algorithms used to sign the certificates in the path are no longer secure. This document describes usage of the SCVP WantBack feature to convey evidence records, enabling SCVP responders to provide preservation evidence for certificates and certificate revocation lists (CRLs). [STANDARDS TRACK] This document is a product of the Long-Term Archive and Notary Services 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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. 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 USC/Information Sciences Institute