idnits 2.17.1 draft-ietf-pkix-dcs-07.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3029 5 Title: Internet X.509 Public Key Infrastructure Data 6 Validation and Certification Server Protocols 7 Author(s): C. Adams, P. Sylvester, M. Zolotarev, 8 R. Zuccherato 9 Status: Experimental 10 Date: February 2001 11 Mailbox: cadams@entrust.com, mzolotarev@baltimore.com, 12 peter.sylvester@edelweb.fr, 13 robert.zuccherato@entrust.com 14 Pages: 51 15 Characters: 107347 16 Updates/Obsoletes/SeeAlso: None 18 I-D Tag: draft-ietf-pkix-dcs-07.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3029.txt 22 This document describes a general Data Validation and Certification 23 Server (DVCS) and the protocols to be used when communicating with 24 it. The Data Validation and Certification Server is a Trusted Third 25 Party (TTP) that can be used as one component in building reliable 26 non-repudiation services. 28 Useful Data Validation and Certification Server responsibilities in a 29 PKI are to assert the validity of signed documents, public key 30 certificates, and the possession or existence of data. 32 Assertions created by this protocol are called Data Validation 33 Certificates (DVC). 35 We give examples of how to use the Data Validation and Certification 36 Server to extend the lifetime of a signature beyond key expiry or 37 revocation and to query the Data Validation and Certification Server 38 regarding the status of a public key certificate. The document 39 includes a complete example of a time stamping transaction. 41 This document is a product of the Public-Key Infrastructure (X.509) 42 Working Group of the IETF. 44 This memo defines an Experimental Protocol for the Internet community. 45 It does not specify an Internet standard of any kind. Discussion and 46 suggestions for improvement are requested. Distribution of this memo 47 is unlimited. 49 This announcement is sent to the IETF list and the RFC-DIST list. 50 Requests to be added to or deleted from the IETF distribution list 51 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 52 added to or deleted from the RFC-DIST distribution list should 53 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 55 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 56 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 57 help: ways_to_get_rfcs. For example: 59 To: rfc-info@RFC-EDITOR.ORG 60 Subject: getting rfcs 62 help: ways_to_get_rfcs 64 Requests for special distribution should be addressed to either the 65 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 66 specifically noted otherwise on the RFC itself, all RFCs are for 67 unlimited distribution.echo 68 Submissions for Requests for Comments should be sent to 69 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 70 Authors, for further information.