RFC 3161 on Time-Stamp Protocol (TSP)
RFC Editor <rfc-ed@isi.edu> Wed, 17 October 2001 19:35 UTC
Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05178 for <pkix-archive@lists.ietf.org>; Wed, 17 Oct 2001 15:35:30 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id f9HIiaP17739 for ietf-pkix-bks; Wed, 17 Oct 2001 11:44:36 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.11.6/8.11.3) with ESMTP id f9HIiYD17735 for <ietf-pkix@imc.org>; Wed, 17 Oct 2001 11:44:34 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03324; Wed, 17 Oct 2001 14:44:32 -0400 (EDT)
Message-Id: <200110171844.OAA03324@ietf.org>
To: IETF-Announce:;
Subject: RFC 3161 on Time-Stamp Protocol (TSP)
Cc: rfc-ed@isi.edu, ietf-pkix@imc.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: RFC Editor <rfc-ed@isi.edu>
Date: Wed, 17 Oct 2001 14:44:32 -0400
Sender: owner-ietf-pkix@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-pkix/mail-archive/>
List-ID: <ietf-pkix.imc.org>
List-Unsubscribe: <mailto:ietf-pkix-request@imc.org?body=unsubscribe>
List-ID: <ietf-pkix.imc.org>
A new Request for Comments is now available in online RFC libraries. RFC 3161 Title: Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP) Author(s): C. Adams, P. Cain, D. Pinkas, R. Zuccherato Status: Standards Track Date: August 2001 Mailbox: cadams@entrust.com, pcain@bbn.com, Denis.Pinkas@bull.net, robert.zuccherato@entrust.com Pages: 26 Characters: 54582 Obsoletes/Updates/SeeAlso: None I-D Tag: draft-ietf-pkix-time-stamp-15.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3161.txt This document describes the format of a request sent to a Time Stamping Authority (TSA) and of the response that is returned. It also establishes several security-relevant requirements for TSA operation, with regards to processing requests to generate responses. This document is a product of the Public-Key Infrastructure (C.509) Working Group of the IETF. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. ----- End Included Message ----- ---------- X-Sun-Data-Type: Multipart X-Sun-Content-Length: 490 X-Sun-Charset: us-ascii X-Sun-Content-Lines: 22 --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <010829162553.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3161 --OtherAccess Content-Type: Message/External-body; name="rfc3161.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <010829162553.RFC@RFC-EDITOR.ORG> --OtherAccess--
- RFC 3161 on Time-Stamp Protocol (TSP) RFC Editor
- RFC 3161 on Time-Stamp Protocol (TSP) RFC Editor
- RFC 3161 on Time-Stamp Protocol (TSP) RFC Editor