RFC 9021: Use of the Walnut Digital Signature Algorithm with CBOR Object Signing and Encryption (COSE)
In plain English — editorial summary, not part of the RFC
This document specifies the conventions for using the Walnut Digital Signature Algorithm (WalnutDSA) for digital signatures with the CBOR Object Signing and Encryption (COSE) syntax. WalnutDSA is a lightweight, quantum-resistant signature scheme based on Group Theoretic Cryptography with implementation and computational efficiency of signature verification in constrained environments, even on 8- and 16-bit platforms. The goal of this publication is to document a way to use the lightweight, quantum-resistant WalnutDSA signature algorithm in COSE in a way that would allow multiple developers to build compatible implementations. As of this publication, the security properties of WalnutDSA have not been evaluated by the IETF and its use has not been endorsed by the IETF. WalnutDSA and the Walnut Digital Signature Algorithm are trademarks of Veridify Security Inc.
Document record
- Document ID
- RFC9021
- Published
- May 2021
- Authors
- D. Atkins
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9052CBOR Object Signing and Encryption (COSE): Structures and ProcessUpdated
August 2022
- RFC 9053CBOR Object Signing and Encryption (COSE): Initial AlgorithmsUpdated
August 2022
- RFC 9528Ephemeral Diffie-Hellman Over COSE (EDHOC)Current
March 2024
- RFC 9597CBOR Web Token (CWT) Claims in COSE HeadersCurrent
June 2024
- RFC 8392CBOR Web Token (CWT)Current
May 2018
- RFC 9942CBOR Object Signing and Encryption (COSE) ReceiptsCurrent
June 2026
- RFC 9943An Architecture for Trustworthy and Transparent Digital Supply ChainsCurrent
June 2026
- RFC 9964ML-DSA for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE)Current
May 2026
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?