RFC 3161: Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)

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…

Read RFC 3161 on the RFC Editor

Incoming relationships (17 related RFCs)

Updated by — RFC 5816: ESSCertIDv2 Update for RFC 3161
Normatively referenced by — RFC 8933: Update to the Cryptographic Message Syntax (CMS) for Algorithm Identifier Protection
Normatively referenced by — RFC 9321: Signature Validation Token
Normatively referenced by — RFC 9921: CBOR Object Signing and Encryption (COSE) Header Parameter for Timestamp Tokens as Defined in RFC 3161
Informatively referenced by — RFC 4949: Internet Security Glossary, Version 2
Informatively referenced by — RFC 4535: GSAKMP: Group Secure Association Key Management Protocol
Informatively referenced by — RFC 6019: BinaryTime: An Alternate Format for Representing Date and Time in ASN.1
Informatively referenced by — RFC 6010: Cryptographic Message Syntax (CMS) Content Constraints Extension
Informatively referenced by — RFC 7299: Object Identifier Registry for the PKIX Working Group
Informatively referenced by — RFC 5485: Digital Signatures on Internet-Draft Documents
Informatively referenced by — RFC 6024: Trust Anchor Management Requirements
Informatively referenced by — RFC 3125: Electronic Signature Policies
Informatively referenced by — RFC 5126: CMS Advanced Electronic Signatures (CAdES)
Informatively referenced by — RFC 3126: Electronic Signature Formats for long term electronic signatures
Informatively referenced by — RFC 4810: Long-Term Archive Service Requirements
Informatively referenced by — RFC 7107: Object Identifier Registry for the S/MIME Mail Security Working Group
Informatively referenced by — RFC 9581: Concise Binary Object Representation (CBOR) Tags for Time, Duration, and Period