RFC 3628: Policy Requirements for Time-Stamping Authorities (TSAs)
In plain English — editorial summary, not part of the RFC
This document defines requirements for a baseline time-stamp policy for Time-Stamping Authorities (TSAs) issuing time-stamp tokens, supported by public key certificates, with an accuracy of one second or better. A TSA may define its own policy which enhances the policy defined in this document. Such a policy shall incorporate or further constrain the requirements identified in this document.
Document record
- Document ID
- RFC3628
- Published
- November 2003
- Authors
- D. Pinkas; N. Pope; J. Ross
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 43
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3620The TUNNEL ProfileUpdated
October 2003
- RFC 3647Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices FrameworkCurrent
November 2003
- RFC 3653XML-Signature XPath Filter 2.0Current
December 2003
- RFC 3602The AES-CBC Cipher Algorithm and Its Use with IPsecCurrent
September 2003
- RFC 3657Use of the Camellia Encryption Algorithm in Cryptographic Message Syntax (CMS)Current
January 2004
- RFC 3664The AES-XCBC-PRF-128 Algorithm for the Internet Key Exchange Protocol (IKE)Obsoleted
January 2004
- RFC 3586IP Security Policy (IPSP) RequirementsCurrent
August 2003
- RFC 3585IPsec Configuration Policy Information ModelCurrent
August 2003
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?