1

A qualified trust service provider under eIDAS uses ESSCertIDv2 for their time stamp tokens, but ESSCertIDv2 was not present in the RFC 3161 specification, it was added later in RFC 5816.

RFC 3161 in 2.4.2 requires ESSCertID:

The certificate identifier (ESSCertID) of the TSA certificate MUST be included as a signerInfo attribute inside a SigningCertificate attribute.

Can a token that uses ESSCertIDv2 instead of ESSCertID be a valid RFC 3161 time stamp token?

Can it be used as a qualified time stamp under eIDAS?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.