Signature Validation Token
RFC 9321, “Signature Validation Token”, is an Informational document published in October 2022 by S. Santesson, R. Housley. The canonical text is published by the RFC Editor.
Abstract
Electronic signatures have a limited lifespan with respect to the time period that they can be validated and determined to be authentic. The Signature Validation Token (SVT) defined in this specification provides evidence that asserts the validity of an electronic signature. The SVT is provided by a trusted authority, which asserts that a particular signature was successfully validated according to defined procedures at a certain time. Any future validation of that electronic signature can be satisfied by validating the SVT without any need to also validate the original electronic signature or the associated digital certificates. The SVT supports electronic signatures in Cryptographic Message Syntax (CMS), XML, PDF, and JSON documents.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 9321 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 9320 Deterministic Networking Bounded Latency
- RFC 9322 In Situ Operations, Administration, and Maintenance Loopback and Active Flags
- RFC 9319 The Use of maxLength in the Resource Public Key Infrastructure
- RFC 9323 A Profile for RPKI Signed Checklists
- RFC 9318 IAB Workshop Report: Measuring Network Quality for End-Users
- RFC 9324 Policy Based on the Resource Public Key Infrastructure without Route Refresh
- RFC 9317 Operational Considerations for Streaming Media
- RFC 9325 Recommendations for Secure Use of Transport Layer Security and Datagram Transport Layer Security