Network Working Group B. Livelsberger, Ed. Internet-Draft 16 April 2026 Intended status: Informational Expires: 18 October 2026 ACVP SLH-DSA JSON Specification draft-livelsberger-acvp-slh-dsa-01 Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on 18 October 2026. Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Table of Contents 1. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 2 2. Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 4.1. Notation conventions . . . . . . . . . . . . . . . . . . 3 4.2. Terms and Definitions . . . . . . . . . . . . . . . . . . 3 4.2.1. Prompt . . . . . . . . . . . . . . . . . . . . . . . 3 4.2.2. Registration . . . . . . . . . . . . . . . . . . . . 4 4.2.3. Response . . . . . . . . . . . . . . . . . . . . . . 4 Livelsberger Expires 18 October 2026 [Page 1] Internet-Draft ACVP SLH-DSA April 2026 4.2.4. Test Case . . . . . . . . . . . . . . . . . . . . . . 4 4.2.5. Test Group . . . . . . . . . . . . . . . . . . . . . 4 4.2.6. Test Vector Set . . . . . . . . . . . . . . . . . . . 4 4.2.7. Validation . . . . . . . . . . . . . . . . . . . . . 4 5. Supported SLH-DSA Algorithms . . . . . . . . . . . . . . . . 4 6. Test Types and Test Coverage . . . . . . . . . . . . . . . . 4 6.1. Test Types . . . . . . . . . . . . . . . . . . . . . . . 5 6.1.1. SLH-DSA KeyGen Test Types . . . . . . . . . . . . . . 5 6.1.2. SLH-DSA SigGen Test Types . . . . . . . . . . . . . . 5 6.1.3. SLH-DSA SigVer Test Types . . . . . . . . . . . . . . 5 6.2. Test Coverage . . . . . . . . . . . . . . . . . . . . . . 6 6.2.1. Requirements Covered . . . . . . . . . . . . . . . . 6 6.2.2. Requirements Not Covered . . . . . . . . . . . . . . 7 7. Capabilities Registration . . . . . . . . . . . . . . . . . . 7 7.1. Prerequisites . . . . . . . . . . . . . . . . . . . . . . 7 7.2. Required Prerequisite Algorithms for SLH-DSA Validations . . . . . . . . . . . . . . . . . . . . . . . 8 7.3. SLH-DSA keyGen Registration Properties . . . . . . . . . 9 7.3.1. SLH-DSA keyGen Mode Capabilities Example . . . . . . 10 7.4. SLH-DSA sigGen Registration Properties . . . . . . . . . 11 7.4.1. SLH-DSA sigGen Mode Capabilities Example . . . . . . 14 7.5. SLH-DSA sigVer Registration Properties . . . . . . . . . 15 7.5.1. Capability JSON Values . . . . . . . . . . . . . . . 16 7.5.2. SLH-DSA sigVer Mode Capabilities Example . . . . . . 18 8. Test Vectors . . . . . . . . . . . . . . . . . . . . . . . . 19 8.1. SLH-DSA keyGen Test Vectors . . . . . . . . . . . . . . . 20 8.1.1. SLH-DSA keyGen Test Groups JSON Schema . . . . . . . 21 8.1.2. SLH-DSA keyGen Test Case JSON Schema . . . . . . . . 21 8.2. SLH-DSA sigGen Test Vectors . . . . . . . . . . . . . . . 23 8.2.1. SLH-DSA sigGen Test Groups JSON Schema . . . . . . . 23 8.2.2. SLH-DSA sigGen Test Case JSON Schema . . . . . . . . 24 8.3. SLH-DSA sigVer Test Vectors . . . . . . . . . . . . . . . 26 8.3.1. SLH-DSA sigVer Test Groups JSON Schema . . . . . . . 26 8.3.2. SLH-DSA sigVer Test Case JSON Schema . . . . . . . . 27 9. Test Vector Responses . . . . . . . . . . . . . . . . . . . . 30 9.1. SLH-DSA keyGen Test Vector Responses . . . . . . . . . . 31 9.2. SLH-DSA sigGen Test Vector Responses . . . . . . . . . . 32 9.3. SLH-DSA sigVer Test Vector Responses . . . . . . . . . . 33 10. Security Considerations . . . . . . . . . . . . . . . . . . . 34 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 12. Normative References . . . . . . . . . . . . . . . . . . . . 34 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 35 1. Acknowledgements There are no acknowledgements. Livelsberger Expires 18 October 2026 [Page 2] Internet-Draft ACVP SLH-DSA April 2026 2. Abstract This document defines the JSON schema for testing Stateless Hash- Based Digital Signature Algorithm (SLH-DSA) implementations with the ACVP specification. 3. Introduction The Automated Crypto Validation Protocol (ACVP) defines a mechanism to automatically verify the cryptographic implementation of a software or hardware crypto module. The ACVP specification defines how a crypto module communicates with an ACVP server, including crypto capabilities negotiation, session management, authentication, vector processing and more. The ACVP specification does not define algorithm specific JSON constructs for performing the crypto validation. A series of ACVP sub-specifications define the constructs for testing individual crypto algorithms. Each sub- specification addresses a specific class of crypto algorithms. This sub-specification defines the JSON constructs for testing Stateless Hash-Based Digital Signature Algorithm (SLH-DSA) implementations using ACVP. This document is a work-product of the NIST (https://www.nist.gov/) Cryptographic Algorithm Validation Program (https://csrc.nist.gov/projects/cryptographic-algorithm-validation- program) (CAVP). Please communicate questions and feedback concerning this document to the CAVP by opening an issue on the usnistgov/ACVP GitHub repository at https://github.com/usnistgov/ACVP/issues. 4. Conventions 4.1. Notation conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "*NOT RECOMMENDED*", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 of [RFC2119] and [RFC8174] when, and only when, they appear in all capitals, as shown here. 4.2. Terms and Definitions 4.2.1. Prompt JSON sent from the server to the client describing the tests the client performs Livelsberger Expires 18 October 2026 [Page 3] Internet-Draft ACVP SLH-DSA April 2026 4.2.2. Registration The initial request from the client to the server describing the capabilities of one or several algorithm, mode and revision combinations 4.2.3. Response JSON sent from the client to the server in response to the prompt 4.2.4. Test Case An individual unit of work within a prompt or response 4.2.5. Test Group A collection of test cases that share similar properties within a prompt or response 4.2.6. Test Vector Set A collection of test groups under a specific algorithm, mode, and revision 4.2.7. Validation JSON sent from the server to the client that specifies the correctness of the response 5. Supported SLH-DSA Algorithms The following SLH-DSA algorithms MAY be advertised by the ACVP compliant cryptographic module. The list is in the form "algorithm / mode / revision". * SLH-DSA / keyGen / FIPS205 * SLH-DSA / sigGen / FIPS205 * SLH-DSA / sigVer / FIPS205 6. Test Types and Test Coverage Livelsberger Expires 18 October 2026 [Page 4] Internet-Draft ACVP SLH-DSA April 2026 6.1. Test Types The ACVP server performs a set of tests on the specified SLH-DSA algorithm in order to assess the correctness and robustness of the implementation. A typical ACVP validation session SHALL require multiple tests to be performed for every supported permutation of SLH-DSA capabilities. This section describes the design of the tests used to validate implementations of the SLH-DSA algorithms. The number of tests MAY vary but the minimum number required by each test type SHALL be included by the server. The test type describes the format of the test rather than the intention of the test. Multiple tests of the same test type MAY cover different assurances regarding the implementation. 6.1.1. SLH-DSA KeyGen Test Types * SLH-DSA / keyGen / * "AFT" - Algorithm Functional Test. For each test case provided the IUT SHALL generate a key pair from provided seed and key values, i.e., SK.seed, SK.prf, and PK.seed. The IUT-computed key pair is communicated to the ACVP server and compared to the expected key pair. This tests the implementation of Algorithm 18 slh_keygen_internal() from [FIPS205] Section 9.1. The server SHALL provide at least 10 tests for each combination of capabilities. 6.1.2. SLH-DSA SigGen Test Types * SLH-DSA / sigGen / * "AFT" - Algorithm Functional Test. For each test case provided the IUT SHALL generate a valid signature given the ACVP-provided private key, message, context (for external interface testing) and randomness (for non-deterministic signature testing). The signature is then compared to the known result by the ACVP server. This tests the implementation of Algorithm 19 slh_sign_internal(), Algorithm 22 slh_sign(), and Algorithm 23 hash_slh_sign() from [FIPS205]. The server SHALL provide at least 13 tests generated for each combination of capabilities. The "hashAlg" capability MAY be excluded from the combination of capabilities due to the number of supported hash functions. Each "hashAlg" provided by the IUT SHALL be covered within the at least 13 tests generated for each combination of capabilities. 6.1.3. SLH-DSA SigVer Test Types * SLH-DSA / sigVer / * "AFT" - Algorithm Functional Test. Livelsberger Expires 18 October 2026 [Page 5] Internet-Draft ACVP SLH-DSA April 2026 The ACVP server generates a series of messages, public keys, and signatures to communicate to the IUT. The IUT SHALL determine the validity of the signature. This tests the implementation of Algorithm 20 slh_verify_internal(), Algorithm 24 slh_verify(), and Algorithm 25 hash_slh_verify() from [FIPS205]. Tests for signature verification are performed by the server modifying a valid signature to obtain specific assurances from the implementation. The server SHALL include at least 2 tests for each modification type (including the no modification valid signature case) for all combinations of capabilities. The "hashAlg" capability MAY be excluded from the combination of capabilities due to the number of supported hash functions. Each "hashAlg" provided by the IUT SHALL be covered within the at least 14 tests generated for each combination of capabilities. The signature modifications are: * "valid signature and message - signature should verify successfully" - No modification is made and the signature is valid. * "modified message" - The message that was signed has been changed. The signature is not valid. * "modified signature - R" - The signature component R has been changed. The signature is not valid. * "modified signature - SIGFORS" - The signature component SIGFORS has been changed. The signature is not valid. * "modified signature - SIGHT" - The signature component SIGHT has been changed. The signature is not valid. * "invalid signature - too long" - The signature is not a valid size due to extra bytes. The signature is not valid. * "invalid signature - too short" - The signature is not a valid size due to missing bytes. The signature is not valid. 6.2. Test Coverage The tests described in this document have the intention of ensuring an implementation is conformant to [FIPS205]. 6.2.1. Requirements Covered * The tests will support ensuring the conformity and correctness of an implementation of the algorithms supported. Livelsberger Expires 18 October 2026 [Page 6] Internet-Draft ACVP SLH-DSA April 2026 6.2.2. Requirements Not Covered * FIPS 205 Section 3.1. Additional Requirements. Requirements outlined in this section are not testable by an ACVP server. An ACVP server will not test that fresh seed values are used for fresh invocations of key generation, that approved deterministic random bit generators (DRBGs) are used with the correct security strengths, that sensitive data is destroyed, that key validation is performed, and that floating point arithmetic is not used. 7. Capabilities Registration ACVP requires crypto modules to register their capabilities. This allows the crypto module to advertise support for specific algorithms, notifying the ACVP server which algorithms need test vectors generated for the validation process. This section describes the constructs for advertising support of SLH-DSA algorithms to the ACVP server. The algorithm capabilities MUST be advertised as JSON objects within the 'algorithms' value of the ACVP registration message. The 'algorithms' value is an array, where each array element is an individual JSON object defined in this section. The 'algorithms' value is part of the 'capability_exchange' element of the ACVP JSON registration message. See the ACVP specification [ACVP] for more details on the registration message. 7.1. Prerequisites Each algorithm implementation MAY rely on other cryptographic primitives. For example, RSA Signature algorithms depend on an underlying hash function. Each of these underlying algorithm primitives must be validated, either separately or as part of the same submission. ACVP provides a mechanism for specifying the required prerequisites: Prerequisites, if applicable, MUST be submitted in the registration as the prereqVals JSON property array inside each element of the algorithms array. Each element in the prereqVals array MUST contain the following properties Livelsberger Expires 18 October 2026 [Page 7] Internet-Draft ACVP SLH-DSA April 2026 +===============+=============================+===========+ | JSON Property | Description | JSON Type | +===============+=============================+===========+ | algorithm | a prerequisite algorithm | string | +---------------+-----------------------------+-----------+ | valValue | algorithm validation number | string | +---------------+-----------------------------+-----------+ Table 1: Prerequisite Properties A "valValue" of "same" SHALL be used to indicate that the prerequisite is being met by a different algorithm in the capability exchange in the same registration. An example description of prerequisites within a single algorithm capability exchange looks like this "prereqVals": [ { "algorithm": "Alg1", "valValue": "Val-1234" }, { "algorithm": "Alg2", "valValue": "same" } ] 7.2. Required Prerequisite Algorithms for SLH-DSA Validations Each SLH-DSA implementation relies on other cryptographic primitives. For example, SLH-DSA keyGen uses an underlying SHA or SHAKE algorithm. Each of these underlying algorithm primitives must be validated, either separately or as part of the same submission. ACVP provides a mechanism for specifying the required prerequisites: Livelsberger Expires 18 October 2026 [Page 8] Internet-Draft ACVP SLH-DSA April 2026 +==============+================+=====================+============+ | JSON Value | Description | JSON Type | Valid | | | | | Values | +==============+================+=====================+============+ | algorithm | a prerequisite | string | SHA, SHAKE | | | algorithm | | or HMAC | +--------------+----------------+---------------------+------------+ | valValue | algorithm | string | Actual | | | validation | | number or | | | number | | "same" | +--------------+----------------+---------------------+------------+ | prereqAlgVal | prerequisite | object with | See above | | | algorithm | algorithm and | | | | validation | valValue properties | | +--------------+----------------+---------------------+------------+ Table 2: Required SLH-DSA Prerequisite Algorithms JSON Values 7.3. SLH-DSA keyGen Registration Properties Each SLH-DSA keyGen algorithm capability advertised is a self- contained JSON object using the following values. Livelsberger Expires 18 October 2026 [Page 9] Internet-Draft ACVP SLH-DSA April 2026 +===============+============+==============+=======================+ | JSON Value |Description | JSON Type | Valid Values | +===============+============+==============+=======================+ | algorithm |The | string | "SLH-DSA" | | |algorithm to| | | | |be validated| | | +---------------+------------+--------------+-----------------------+ | mode |The SLH-DSA | string | "keyGen" | | |mode to be | | | | |validated | | | +---------------+------------+--------------+-----------------------+ | revision |The | string | "FIPS205" | | |algorithm | | | | |testing | | | | |revision to | | | | |use | | | +---------------+------------+--------------+-----------------------+ | prereqVals |Prerequisite| array of | See Section 7.2 | | |algorithm | prereqAlgVal | | | |validations | objects | | +---------------+------------+--------------+-----------------------+ | parameterSets |The SLH-DSA | array of | "SLH-DSA-SHA2-128s", | | |parameter | strings | "SLH-DSA-SHA2-128f", | | |sets | | "SLH-DSA-SHA2-192s", | | |supported. | | "SLH-DSA-SHA2-192f", | | | | | "SLH-DSA-SHA2-256s", | | | | | "SLH-DSA-SHA2-256f", | | | | | "SLH-DSA-SHAKE-128s", | | | | | "SLH-DSA-SHAKE-128f", | | | | | "SLH-DSA-SHAKE-192s", | | | | | "SLH-DSA-SHAKE-192f", | | | | | "SLH-DSA-SHAKE-256s", | | | | | "SLH-DSA-SHAKE-256f" | +---------------+------------+--------------+-----------------------+ Table 3: SLH-DSA keyGen Algorithm Capabilities JSON Values 7.3.1. SLH-DSA keyGen Mode Capabilities Example Below is an example of the registration for SLH-DSA / keyGen / FIPS205 Livelsberger Expires 18 October 2026 [Page 10] Internet-Draft ACVP SLH-DSA April 2026 { "algorithm": "SLH-DSA", "mode": "keyGen", "revision": "FIPS205", "prereqVals": [ { "algorithm": "SHA2-256", "valValue": "123456" }, { "algorithm": "SHA2-512", "valValue": "123456" }, { "algorithm": "SHAKE256", "valValue": "123456" } ], "parameterSets": [ "SLH-DSA-SHA2-128s", "SLH-DSA-SHA2-192f", "SLH-DSA-SHAKE-192s", "SLH-DSA-SHAKE-256f" ] } 7.4. SLH-DSA sigGen Registration Properties Each SLH-DSA sigGen algorithm capability advertised is a self- contained JSON object using the following values. +=====================+===================+=============+===========+ | JSON Value |Description |JSON Type |Valid | | | | |Values | +=====================+===================+=============+===========+ | algorithm |The algorithm to be|string |"SLH-DSA" | | |validated | | | +---------------------+-------------------+-------------+-----------+ | mode |The SLH-DSA mode to|string |"sigGen" | | |be validated | | | +---------------------+-------------------+-------------+-----------+ | revision |The algorithm |string |"FIPS205" | | |testing revision to| | | | |use | | | +---------------------+-------------------+-------------+-----------+ | prereqVals |Prerequisite |array of |See | | |algorithm |prereqAlgVal |Section 7.2| | |validations |objects | | +---------------------+-------------------+-------------+-----------+ | capabilities |The capabilities of|array of |See Table 5| | |the implementation.|capability | | Livelsberger Expires 18 October 2026 [Page 11] Internet-Draft ACVP SLH-DSA April 2026 | |Pairs of parameter |objects | | | |sets and associated| | | | |supported message | | | | |lengths. | | | +---------------------+-------------------+-------------+-----------+ | signatureInterfaces |The SLH-DSA |array of |"internal",| | |signature |strings |"external" | | |interfaces | | | | |supported | | | +---------------------+-------------------+-------------+-----------+ | preHash |Whether SLH-DSA or |array of |"pure", | | |HashSLH-DSA are |strings |"preHash" | | |supported | | | +---------------------+-------------------+-------------+-----------+ | deterministic |The SLH-DSA |array of |true, false| | |signature |booleans | | | |generation variants| | | | |supported. A value| | | | |of "true" indicates| | | | |that deterministic | | | | |signature | | | | |generation is | | | | |supported and a | | | | |value of "false" | | | | |indicates that non-| | | | |deterministic | | | | |signature | | | | |generation is | | | | |supported. | | | +---------------------+-------------------+-------------+-----------+ Table 4: SLH-DSA sigGen Algorithm Capabilities JSON Values Each capability advertised is a self-contained JSON object using the following values. Livelsberger Expires 18 October 2026 [Page 12] Internet-Draft ACVP SLH-DSA April 2026 +===============+=============+=========+=======================+ | JSON Value | Description | JSON | Valid Values | | | | Type | | +===============+=============+=========+=======================+ | parameterSets | The SLH-DSA | array | "SLH-DSA-SHA2-128s", | | | parameter | of | "SLH-DSA-SHA2-128f", | | | sets | strings | "SLH-DSA-SHA2-192s", | | | supported | | "SLH-DSA-SHA2-192f", | | | | | "SLH-DSA-SHA2-256s", | | | | | "SLH-DSA-SHA2-256f", | | | | | "SLH-DSA-SHAKE-128s", | | | | | "SLH-DSA-SHAKE-128f", | | | | | "SLH-DSA-SHAKE-192s", | | | | | "SLH-DSA-SHAKE-192f", | | | | | "SLH-DSA-SHAKE-256s", | | | | | "SLH-DSA-SHAKE-256f" | +---------------+-------------+---------+-----------------------+ | messageLength | The | domain | Min: 8, Max: 65536, | | | supported | | Incr: 8 | | | message | | | | | lengths in | | | | | bits | | | +---------------+-------------+---------+-----------------------+ | hashAlgs | The hash | array | "SHA2-224", | | | algorithms | of | "SHA2-256", | | | used if | strings | "SHA2-384", | | | preHash | | "SHA2-512", | | | SLH-DSA is | | "SHA2-512/224", | | | used | | "SHA2-512/256", | | | | | "SHA3-224", | | | | | "SHA3-256", | | | | | "SHA3-384", | | | | | "SHA3-512", "SHAKE- | | | | | 128", "SHAKE-256" | +---------------+-------------+---------+-----------------------+ | contextLength | The | domain | Min: 0, Max: 2040, | | | supported | | Incr: 8 | | | context | | | | | lengths if | | | | | the | | | | | external | | | | | interface | | | | | is used | | | +---------------+-------------+---------+-----------------------+ Table 5: Registration SLH-DSA sigGen Capability JSON Values Livelsberger Expires 18 October 2026 [Page 13] Internet-Draft ACVP SLH-DSA April 2026 7.4.1. SLH-DSA sigGen Mode Capabilities Example Below is an example of the registration for SLH-DSA / sigGen / FIPS205 { "algorithm": "SLH-DSA", "mode": "sigGen", "revision": "FIPS205", "prereqVals": [ { "algorithm": "SHA", "valValue": "123456" } ], "deterministic": [ true, false ], "signatureInterfaces": [ "external", "internal" ], "preHash": [ "pure", "preHash" ], "capabilities": [ { "parameterSets": [ "SLH-DSA-SHA2-128f", "SLH-DSA-SHA2-192f", "SLH-DSA-SHA2-256f" ], "messageLength": [ { "min": 8, "max": 65536, "increment": 8 } ], "hashAlgs": [ "SHA2-256" ], "contextLength": [ { "min": 0, "max": 2040, Livelsberger Expires 18 October 2026 [Page 14] Internet-Draft ACVP SLH-DSA April 2026 "increment": 8 } ] }, { "parameterSets": [ "SLH-DSA-SHAKE-128s", "SLH-DSA-SHAKE-192s", "SLH-DSA-SHAKE-256s" ], "messageLength": [ { "min": 8, "max": 65536, "increment": 8 } ], "hashAlgs": [ "SHA3-512" ], "contextLength": [ { "min": 0, "max": 2040, "increment": 8 } ] } ] } 7.5. SLH-DSA sigVer Registration Properties Each SLH-DSA sigVer algorithm capability advertised is a self- contained JSON object using the following values. Livelsberger Expires 18 October 2026 [Page 15] Internet-Draft ACVP SLH-DSA April 2026 +=====================+=================+==============+============+ | JSON Value |Description | JSON Type |Valid Values| +=====================+=================+==============+============+ | algorithm |The algorithm to | string |"SLH-DSA" | | |be validated | | | +---------------------+-----------------+--------------+------------+ | mode |The SLH-DSA mode | string |"sigVer" | | |to be validated | | | +---------------------+-----------------+--------------+------------+ | revision |The algorithm | string |"FIPS205" | | |testing revision | | | | |to use | | | +---------------------+-----------------+--------------+------------+ | prereqVals |Prerequisite | array of |See | | |algorithm | prereqAlgVal |Section 7.2 | | |validations | objects | | +---------------------+-----------------+--------------+------------+ | capabilities |The capabilities | array of |See Table 7 | | |of the | capability | | | |implementation. | objects | | | |Pairs of | | | | |parameter sets | | | | |and associated | | | | |supported message| | | | |lengths. | | | +---------------------+-----------------+--------------+------------+ | signatureInterfaces |The SLH-DSA | array of |"internal", | | |signature | strings |"external" | | |interfaces | | | | |supported | | | +---------------------+-----------------+--------------+------------+ | preHash |Whether SLH-DSA | array of |"pure", | | |or HashSLH-DSA | strings |"preHash" | | |are supported | | | +---------------------+-----------------+--------------+------------+ Table 6: SLH-DSA sigVer Algorithm Capabilities JSON Values 7.5.1. Capability JSON Values Each capability advertised is a self-contained JSON object using the following values. Livelsberger Expires 18 October 2026 [Page 16] Internet-Draft ACVP SLH-DSA April 2026 +===============+=============+=========+=======================+ | JSON Value | Description | JSON | Valid Values | | | | Type | | +===============+=============+=========+=======================+ | parameterSets | The SLH-DSA | array | "SLH-DSA-SHA2-128s", | | | parameter | of | "SLH-DSA-SHA2-128f", | | | sets | strings | "SLH-DSA-SHA2-192s", | | | supported | | "SLH-DSA-SHA2-192f", | | | | | "SLH-DSA-SHA2-256s", | | | | | "SLH-DSA-SHA2-256f", | | | | | "SLH-DSA-SHAKE-128s", | | | | | "SLH-DSA-SHAKE-128f", | | | | | "SLH-DSA-SHAKE-192s", | | | | | "SLH-DSA-SHAKE-192f", | | | | | "SLH-DSA-SHAKE-256s", | | | | | "SLH-DSA-SHAKE-256f" | +---------------+-------------+---------+-----------------------+ | messageLength | The | domain | Min: 8, Max: 65536, | | | supported | | Incr: 8 | | | message | | | | | lengths in | | | | | bits | | | +---------------+-------------+---------+-----------------------+ | hashAlgs | The hash | array | "SHA2-224", | | | algorithms | of | "SHA2-256", | | | used if | strings | "SHA2-384", | | | preHash | | "SHA2-512", | | | SLH-DSA is | | "SHA2-512/224", | | | used | | "SHA2-512/256", | | | | | "SHA3-224", | | | | | "SHA3-256", | | | | | "SHA3-384", | | | | | "SHA3-512", "SHAKE- | | | | | 128", "SHAKE-256" | +---------------+-------------+---------+-----------------------+ | contextLength | The | domain | Min: 0, Max: 2040, | | | supported | | Incr: 8 | | | context | | | | | lengths if | | | | | the | | | | | external | | | | | interface | | | | | is used | | | +---------------+-------------+---------+-----------------------+ Table 7: Registration SLH-DSA sigVer Capability JSON Values Livelsberger Expires 18 October 2026 [Page 17] Internet-Draft ACVP SLH-DSA April 2026 7.5.2. SLH-DSA sigVer Mode Capabilities Example Below is an example of the registration for SLH-DSA / sigVer / FIPS205 { "algorithm": "SLH-DSA", "mode": "sigVer", "revision": "FIPS205", "prereqVals": [ { "algorithm": "SHA", "valValue": "123456" } ], "signatureInterfaces": [ "external", "internal" ], "preHash": [ "pure", "preHash" ], "capabilities": [ { "parameterSets": [ "SLH-DSA-SHA2-128f", "SLH-DSA-SHA2-192f", "SLH-DSA-SHA2-256f" ], "messageLength": [ { "min": 8, "max": 65536, "increment": 8 } ], "hashAlgs": [ "SHA2-256" ], "contextLength": [ { "min": 0, "max": 2040, "increment": 8 } ] }, Livelsberger Expires 18 October 2026 [Page 18] Internet-Draft ACVP SLH-DSA April 2026 { "parameterSets": [ "SLH-DSA-SHAKE-128s", "SLH-DSA-SHAKE-192s", "SLH-DSA-SHAKE-256s" ], "messageLength": [ { "min": 8, "max": 65536, "increment": 8 } ], "hashAlgs": [ "SHA3-512" ], "contextLength": [ { "min": 0, "max": 2040, "increment": 8 } ] } ] } 8. Test Vectors The ACVP server provides test vectors to the ACVP client, which are then processed and returned to the ACVP server for validation. A typical ACVP validation test session would require multiple test vector sets to be downloaded and processed by the ACVP client. Each test vector set represents an individual cryptographic algorithm defined during the capability exchange. This section describes the JSON schema for a test vector set used with Stateless Hash-Based Digital Signature Algorithm (SLH-DSA) algorithms. The test vector set JSON schema is a multi-level hierarchy that contains meta data for the entire vector set as well as individual test vectors to be processed by the ACVP client. The following table describes the JSON elements at the top level of the hierarchy. Livelsberger Expires 18 October 2026 [Page 19] Internet-Draft ACVP SLH-DSA April 2026 +============+================================+=========+ | JSON | Description | JSON | | Values | | Type | +============+================================+=========+ | acvVersion | Protocol version identifier | string | +------------+--------------------------------+---------+ | vsId | Unique numeric vector set | integer | | | identifier | | +------------+--------------------------------+---------+ | algorithm | Algorithm defined in the | string | | | capability exchange | | +------------+--------------------------------+---------+ | mode | Mode defined in the capability | string | | | exchange | | +------------+--------------------------------+---------+ | revision | Protocol test revision | string | | | selected | | +------------+--------------------------------+---------+ | testGroups | Array of test group JSON | array | | | objects. Depending on the | | | | algorithm, see Section 8.1.1, | | | | Section 8.2.1 or Section 8.3.1 | | +------------+--------------------------------+---------+ Table 8: Top Level Test Vector JSON Elements An example of this would look like this [ { "acvVersion": }, { "vsId": 1, "algorithm": "Alg1", "mode": "Mode1", "revision": "Revision1.0", "testGroups": [ ... ] } ] 8.1. SLH-DSA keyGen Test Vectors Livelsberger Expires 18 October 2026 [Page 20] Internet-Draft ACVP SLH-DSA April 2026 8.1.1. SLH-DSA keyGen Test Groups JSON Schema The testGroups element at the top level in the test vector JSON object is an array of test groups. Test vectors are grouped into similar test cases to reduce the amount of data transmitted in the vector set. For instance, all test vectors that use the same key size would be grouped together. The Test Group JSON object contains meta data that applies to all test vectors within the group. The following table describes the SLH-DSA JSON elements of the Test Group JSON object. The test group for SLH-DSA / keyGen / FIPS205 is as follows: +==============+========================================+=========+ | JSON Value | Description | JSON | | | | type | +==============+========================================+=========+ | tgId | Numeric identifier for the test group, | integer | | | unique across the entire vector set | | +--------------+----------------------------------------+---------+ | testType | The test operation performed | string | +--------------+----------------------------------------+---------+ | parameterSet | The SLH-DSA parameter set used | string | +--------------+----------------------------------------+---------+ | tests | Array of individual test vector JSON | array | | | objects, which are defined in | | | | Section 8.1.2 | | +--------------+----------------------------------------+---------+ Table 9: SLH-DSA keyGen Test Group JSON Object 8.1.2. SLH-DSA keyGen Test Case JSON Schema Each test group contains an array of one or more test cases. Each test case is a JSON object that represents a single test vector to be processed by the ACVP client. The following table describes the JSON elements for each SLH-DSA / keyGen / FIPS205 test vector. Livelsberger Expires 18 October 2026 [Page 21] Internet-Draft ACVP SLH-DSA April 2026 +============+=======================================+===========+ | JSON Value | Description | JSON type | +============+=======================================+===========+ | tcId | Numeric identifier for the test case, | integer | | | unique across the entire vector set | | +------------+---------------------------------------+-----------+ | skSeed | Private seed value | hex | +------------+---------------------------------------+-----------+ | skPrf | PRF key value | hex | +------------+---------------------------------------+-----------+ | pkSeed | Public seed value | hex | +------------+---------------------------------------+-----------+ Table 10: SLH-DSA keyGen Test Case JSON Object The following is an example JSON object sent from the server to the client for SLH-DSA / keyGen / FIPS205. [ { "acvVersion": }, { "vsId": 1564, "algorithm": "SLH-DSA", "mode": "keyGen", "revision": "FIPS205", "testGroups": [ { "tgId": 1, "testType": "AFT", "parameterSet": "SLH-DSA-SHA2-128s", "tests": [ { "tcId": 1, "skSeed": "2F896D61D9CD9038CA303394FADAA22A", "skPrf": "24AC5EC1D86A989CA2196C3C8632419C", "pkSeed": "1A05A42FE300E87B16AEE116CB2E2363" } ] } ] } ] Livelsberger Expires 18 October 2026 [Page 22] Internet-Draft ACVP SLH-DSA April 2026 8.2. SLH-DSA sigGen Test Vectors 8.2.1. SLH-DSA sigGen Test Groups JSON Schema The testGroups element at the top level in the test vector JSON object is an array of test groups. Test vectors are grouped into similar test cases to reduce the amount of data transmitted in the vector set. For instance, all test vectors that use the same key size would be grouped together. The Test Group JSON object contains meta data that applies to all test vectors within the group. The following table describes the SLH-DSA JSON elements of the Test Group JSON object. The test group for SLH-DSA / sigGen / FIPS205 is as follows: +====================+===================================+=========+ | JSON Value | Description | JSON | | | | type | +====================+===================================+=========+ | tgId | Numeric identifier for the test | integer | | | group, unique across the entire | | | | vector set | | +--------------------+-----------------------------------+---------+ | testType | The test operation performed | string | +--------------------+-----------------------------------+---------+ | parameterSet | The SLH-DSA parameter set used | string | +--------------------+-----------------------------------+---------+ | deterministic | Whether the signatures should be | boolean | | | generated using the deterministic | | | | or non-deterministic signature | | | | generation variant | | +--------------------+-----------------------------------+---------+ | signatureInterface | Whether the signature is | string | | | generated using the internal or | | | | external routine | | +--------------------+-----------------------------------+---------+ | preHash | Whether the signature is | string | | | generated using the prehash or | | | | pure routine | | +--------------------+-----------------------------------+---------+ | tests | Array of individual test vector | array | | | JSON objects, which are defined | | | | in Section 8.2.2 | | +--------------------+-----------------------------------+---------+ Table 11: SLH-DSA sigGen Test Group JSON Object Livelsberger Expires 18 October 2026 [Page 23] Internet-Draft ACVP SLH-DSA April 2026 | NOTE: The "preHash" property will only be present if | "signatureInterface" is set to "external". 8.2.2. SLH-DSA sigGen Test Case JSON Schema Each test group contains an array of one or more test cases. Each test case is a JSON object that represents a single test vector to be processed by the ACVP client. The following table describes the JSON elements for each SLH-DSA / sigGen / FIPS205 test vector. +======================+===============================+=========+ | JSON Value | Description | JSON | | | | type | +======================+===============================+=========+ | tcId | Numeric identifier for the | integer | | | test case, unique across the | | | | entire vector set | | +----------------------+-------------------------------+---------+ | sk | The secret key that should be | hex | | | used to generate a signature | | +----------------------+-------------------------------+---------+ | additionalRandomness | Additional randomness used by | hex | | | the non-deterministic SLH-DSA | | | | signature generation variant. | | | | Only present for test groups | | | | where "deterministic": false. | | +----------------------+-------------------------------+---------+ | message | The message used to generate | hex | | | the signature | | +----------------------+-------------------------------+---------+ | context | When the test group property | hex | | | "signatureInterface": | | | | "external", the context used | | | | to construct the signed | | | | message | | +----------------------+-------------------------------+---------+ | hashAlg | When the test group property | string | | | "preHash": "preHash", the | | | | hash function used to | | | | construct the signed message | | +----------------------+-------------------------------+---------+ Table 12: SLH-DSA sigGen Test Case JSON Object The following is an example JSON object sent from the server to the client for SLH-DSA / sigGen / FIPS205. Livelsberger Expires 18 October 2026 [Page 24] Internet-Draft ACVP SLH-DSA April 2026 [ { "acvVersion": }, { "vsId": 0, "algorithm": "SLH-DSA", "mode": "sigGen", "revision": "FIPS205", "testGroups": [ { "tgId": 1, "testType": "AFT", "parameterSet": "SLH-DSA-SHA2-192s", "signatureInterface": "internal", "deterministic": true, "tests": [ { "tcId": 1, "sk": "68A103...", "message": "EC1EF9E3B24E..." } ] }, { "tgId": 2, "testType": "AFT", "parameterSet": "SLH-DSA-SHA2-192s", "deterministic": false, "signatureInterface": "external", "preHash": "pure", "tests": [ { "tcId": 15, "sk": "D4E36A5...", "additionalRandomness": "FAFF13...", "message": "34F4B...", "context": "ABCD" } ] }, { "tgId": 3, "testType": "AFT", "parameterSet": "SLH-DSA-SHA2-192s", "deterministic": false, "signatureInterface": "external", "preHash": "preHash", Livelsberger Expires 18 October 2026 [Page 25] Internet-Draft ACVP SLH-DSA April 2026 "tests": [ { "tcId": 15, "sk": "D4E36A5...", "additionalRandomness": "FAFF13...", "message": "34F4B...", "context": "01", "hashAlg": "SHA2-256" } ] } ] } ] 8.3. SLH-DSA sigVer Test Vectors 8.3.1. SLH-DSA sigVer Test Groups JSON Schema The testGroups element at the top level in the test vector JSON object is an array of test groups. Test vectors are grouped into similar test cases to reduce the amount of data transmitted in the vector set. For instance, all test vectors that use the same key size would be grouped together. The Test Group JSON object contains meta data that applies to all test vectors within the group. The following table describes the SLH-DSA JSON elements of the Test Group JSON object. The test group for SLH-DSA / sigVer / FIPS205 is as follows: Livelsberger Expires 18 October 2026 [Page 26] Internet-Draft ACVP SLH-DSA April 2026 +====================+==============================+=========+ | JSON Value | Description | JSON | | | | type | +====================+==============================+=========+ | tgId | Numeric identifier for the | integer | | | test group, unique across | | | | the entire vector set | | +--------------------+------------------------------+---------+ | testType | The test operation performed | string | +--------------------+------------------------------+---------+ | parameterSet | The SLH-DSA parameter set | string | | | used | | +--------------------+------------------------------+---------+ | signatureInterface | Whether the signature is | string | | | generated using the internal | | | | or external routine | | +--------------------+------------------------------+---------+ | preHash | Whether the signature is | string | | | generated using the prehash | | | | or pure routine | | +--------------------+------------------------------+---------+ | tests | Array of individual test | array | | | vector JSON objects, which | | | | are defined in Section 8.3.2 | | +--------------------+------------------------------+---------+ Table 13: SLH-DSA sigVer Test Group JSON Object | NOTE: The "preHash" property will only be present if | "signatureInterface" is set to "external". 8.3.2. SLH-DSA sigVer Test Case JSON Schema Each test group contains an array of one or more test cases. Each test case is a JSON object that represents a single test vector to be processed by the ACVP client. The following table describes the JSON elements for each SLH-DSA / sigVer / FIPS205 test vector. Livelsberger Expires 18 October 2026 [Page 27] Internet-Draft ACVP SLH-DSA April 2026 +===========+=================================+=========+ | JSON | Description | JSON | | Value | | type | +===========+=================================+=========+ | tcId | Numeric identifier for the test | integer | | | case, unique across the entire | | | | vector set | | +-----------+---------------------------------+---------+ | pk | The public key to use to verify | hex | | | the signature | | +-----------+---------------------------------+---------+ | message | The message used to verify with | hex | | | the signature | | +-----------+---------------------------------+---------+ | context | When the test group property | hex | | | "signatureInterface": | | | | "external", the context used to | | | | construct the signed message | | +-----------+---------------------------------+---------+ | hashAlg | When the test group property | string | | | "preHash": "preHash", the hash | | | | function used to construct the | | | | signed message | | +-----------+---------------------------------+---------+ | signature | The signature to verify | hex | +-----------+---------------------------------+---------+ Table 14: SLH-DSA sigVer Test Case JSON Object The following is an example JSON object sent from the server to the client for SLH-DSA / sigVer / FIPS205. [ { "acvVersion": }, { "vsId": 0, "algorithm": "SLH-DSA", "mode": "sigVer", "revision": "FIPS205", "testGroups": [ { "tgId": 1, "testType": "AFT", "parameterSet": "SLH-DSA-SHA2-192s", "signatureInterface": "internal", "tests": [ Livelsberger Expires 18 October 2026 [Page 28] Internet-Draft ACVP SLH-DSA April 2026 { "tcId": 1, "pk": "6CB59...", "message": "4F0D7...", "signature": "C29A11B6C..." }, { "tcId": 2, "pk": "123ABC...", "message": "8479", "signature": "6A99215FC2..." } ] }, { "tgId": 2, "testType": "AFT", "parameterSet": "SLH-DSA-SHA2-192s", "signatureInterface": "external", "preHash": "preHash", "tests": [ { "tcId": 3, "pk": "6CB59...", "message": "4F0D7...", "context": "ABCD", "hashAlg": "SHA2-256", "signature": "C29A11B6C..." }, { "tcId": 4, "pk": "123ABC...", "message": "8479", "context": "ABCD", "hashAlg": "SHA2-256", "signature": "6A99215FC2..." } ] }, { "tgId": 3, "testType": "AFT", "parameterSet": "SLH-DSA-SHA2-192s", "signatureInterface": "external", "preHash": "pure", "tests": [ { "tcId": 5, Livelsberger Expires 18 October 2026 [Page 29] Internet-Draft ACVP SLH-DSA April 2026 "pk": "6CB59...", "message": "4F0D7...", "context": "ABCD", "signature": "C29A11B6C..." }, { "tcId": 6, "pk": "123ABC...", "message": "8479", "context": "ABCD", "signature": "6A99215FC2..." } ] } ] } ] 9. Test Vector Responses After the ACVP client downloads and processes a vector set, it must send the response vectors back to the ACVP server. The following table describes the JSON object that represents a vector set response. +===============+============================+===========+ | JSON Property | Description | JSON Type | +===============+============================+===========+ | acvVersion | The ACVP version used | string | +---------------+----------------------------+-----------+ | vsId | The vector set identifier | integer | +---------------+----------------------------+-----------+ | testGroups | The test group objects in | array | | | the response, see Table 16 | | +---------------+----------------------------+-----------+ Table 15: Response JSON Object An example of this is the following { "acvVersion": "version", "vsId": 1, "testGroups": [ ... ] } The 'testGroups' section is used to organize the ACVP client response in a similar manner to how it distributes vectors. Livelsberger Expires 18 October 2026 [Page 30] Internet-Draft ACVP SLH-DSA April 2026 +==========+========================================+=========+ | JSON | Description | JSON | | Property | | Type | +==========+========================================+=========+ | tgId | The test group identifier | integer | +----------+----------------------------------------+---------+ | tests | The test case objects in the response. | array | | | Depending on the algorithm, see | | | | Table 17, Table 18, or Table 19 | | +----------+----------------------------------------+---------+ Table 16: Response Group Objects An example of this is the following { "tgId": 1, "tests": [ ... ] } 9.1. SLH-DSA keyGen Test Vector Responses Each test group contains an array of one or more test cases. Each test case is a JSON object that represents the results of an ACVP client processing a single test vector. The following table describes the JSON elements for each SLH-DSA / keyGen / FIPS205 test vector. +============+==========================+===========+ | JSON Value | Description | JSON type | +============+==========================+===========+ | tcId | The test case identifier | integer | +------------+--------------------------+-----------+ | pk | The computed public key | hex | +------------+--------------------------+-----------+ | sk | The computed secret key | hex | +------------+--------------------------+-----------+ Table 17: SLH-DSA keyGen Test Case Response JSON Object The following is an example JSON test vector response object for SLH- DSA / keyGen / FIPS205. Livelsberger Expires 18 October 2026 [Page 31] Internet-Draft ACVP SLH-DSA April 2026 [ { "acvVersion": }, { "vsId": 0, "testGroups": [ { "tgId": 1, "tests": [ { "tcId": 1, "pk": "1012798...", "sk": "1012798..." } ] } ] } ] 9.2. SLH-DSA sigGen Test Vector Responses Each test group contains an array of one or more test cases. Each test case is a JSON object that represents the results of an ACVP client processing a single test vector. The following table describes the JSON elements for each SLH-DSA / sigGen / FIPS205 test vector. +============+==========================+===========+ | JSON Value | Description | JSON type | +============+==========================+===========+ | tcId | The test case identifier | integer | +------------+--------------------------+-----------+ | signature | The generated signature | hex | +------------+--------------------------+-----------+ Table 18: SLH-DSA sigGen Test Case Response JSON Object The following is an example JSON test vector response object for SLH- DSA / sigGen / FIPS205. Livelsberger Expires 18 October 2026 [Page 32] Internet-Draft ACVP SLH-DSA April 2026 [ { "acvVersion": }, { "vsId": 1564, "testGroups": [ { "tgId": 1, "tests": [ { "tcId": 1, "signature": "D7D4275..." } ] } ] } ] 9.3. SLH-DSA sigVer Test Vector Responses Each test group contains an array of one or more test cases. Each test case is a JSON object that represents the results of an ACVP client processing a single test vector. The following table describes the JSON elements for each SLH-DSA / sigVer / FIPS205 test vector. +============+=======================================+===========+ | JSON Value | Description | JSON type | +============+=======================================+===========+ | tcId | The test case identifier | integer | +------------+---------------------------------------+-----------+ | testPassed | Whether or not the signature verified | boolean | +------------+---------------------------------------+-----------+ Table 19: SLH-DSA sigVer Test Case Response JSON Object The following is an example JSON test vector response object for SLH- DSA / sigVer / FIPS205. Livelsberger Expires 18 October 2026 [Page 33] Internet-Draft ACVP SLH-DSA April 2026 [ { "acvVersion": }, { "vsId": 0, "testGroups": [ { "tgId": 1, "tests": [ { "tcId": 1, "testPassed": false } ] } ] } ] 10. Security Considerations There are no additional security considerations outside of those outlined in the ACVP document. 11. IANA Considerations This document does not require any action by IANA. 12. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", RFC 8174, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [FIPS205] National Institute of Standards and Technology, "Stateless Hash-Based Digital Signature Standard", NIST FIPS 205, August 2024, . [ACVP] Fussell, B., Vassilev, A., and H. Booth, "Automatic Cryptographic Validation Protocol", ACVP, 1 July 2019. Livelsberger Expires 18 October 2026 [Page 34] Internet-Draft ACVP SLH-DSA April 2026 Author's Address Benjamin Livelsberger (editor) Email: benjamin.livelsberger@nist.gov Livelsberger Expires 18 October 2026 [Page 35]