RFC 9802: Use of the HSS and XMSS Hash-Based Signature Algorithms in Internet X.509 Public Key Infrastructure
In plain English — editorial summary, not part of the RFC
This document specifies algorithm identifiers and ASN.1 encoding formats for the following stateful Hash-Based Signature (HBS) schemes: Hierarchical Signature System (HSS), eXtended Merkle Signature Scheme (XMSS), and XMSS^MT (a multi-tree variant of XMSS). This specification applies to the Internet X.509 Public Key Infrastructure (PKI) when digital signatures are used to sign certificates and certificate revocation lists (CRLs).
Document record
- Document ID
- RFC9802
- Published
- June 2025
- Authors
- D. Van Geest; K. Bashiri; S. Fluhrer; S. Gazdag; S. Kousidis
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9881Internet X.509 Public Key Infrastructure -- Algorithm Identifiers for the Module-Lattice-Based Digital Signature Algorithm (ML-DSA)Current
October 2025
- RFC 9935Internet X.509 Public Key Infrastructure - Algorithm Identifiers for the Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM)Current
March 2026
- RFC 4490Using the GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94, and GOST R 34.10-2001 Algorithms with Cryptographic Message Syntax (CMS)Current
May 2006
- RFC 9763Related Certificates for Use in Multiple Authentications within a ProtocolCurrent
June 2025
- RFC 9734X.509 Certificate Extended Key Usage (EKU) for Instant Messaging URIsCurrent
February 2025
- RFC 9295Clarifications for Ed25519, Ed448, X25519, and X448 Algorithm IdentifiersCurrent
September 2022
- RFC 9216S/MIME Example Keys and CertificatesCurrent
April 2022
- RFC 8813Clarifications for Elliptic Curve Cryptography Subject Public Key InformationCurrent
August 2020
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?