TimeStamping Service is a service that issues time-stamps. Time-stamps confirm that the data existed at a specific time. The service has been described in Internet standard RFC-3161 (http://www.ietf.org/rfc/rfc3161.txt).
Time-Stamping service is a simple client-server system, where a time-stamping service client sends the time-stamping request to the service (server) to verify the existence of a set of data in specific time. Time-Stamping service then returns a digitally signed confirmation of data existence in time. Time-Stamping service is a HTTP service and time-stamping requests are submitted as HTTP POST queries.
Test Time-Stamping service is located at: http://demo.sk.ee/tsa/
Time-Stamping service parameters are the following:
- supported hash algorithms for time-stamping requests: SHA256, SHA384, SHA512,
- digital signature key parameters for signing time-stamps: 2048bit RSA,
- digital signature algorithm for signing time-stamps: SHA512withRSA,
- time-stamping service policy OID: 0.4.0.2023.1.1,
- repository for Time-Stamping Authority Practice Statement: https://www.sk.ee/en/repository/tsa,
- supported time-stamping service policies for requests: 0.4.0.2023.1.1,
- supported time-stamping service extensions for requests: not specified.
Service replies to correct requests include:
- status info – Operation Okay,
- hash algorithm used for signing,
- time-stamp policy OID,
- time-stamp time,
- time-stamping service certificate along with a full certificate chain,
- used extensions,
- nonce value.
Service replies to incorrect requests include::
- status info – Rejected,
- cause of error.
Service checks the time-stamping request’s validity and in case of invalid requests the HTTP status code reply is: 400 – Bad Request.