RFC 9336: X.509 Certificate General-Purpose Extended Key Usage (EKU) for Document Signing
In plain English — editorial summary, not part of the RFC
RFC 5280 specifies several extended key purpose identifiers (KeyPurposeIds) for X.509 certificates. This document defines a general-purpose Document-Signing KeyPurposeId for inclusion in the Extended Key Usage (EKU) extension of X.509 public key certificates. Document-Signing applications may require that the EKU extension be present and that a Document-Signing KeyPurposeId be indicated in order for the certificate to be acceptable to that Document-Signing application.
Document record
- Document ID
- RFC9336
- Published
- December 2022
- Authors
- T. Ito; T. Okubo; S. Turner
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9295Clarifications for Ed25519, Ed448, X25519, and X448 Algorithm IdentifiersCurrent
September 2022
- RFC 9399Internet X.509 Public Key Infrastructure: Logotypes in X.509 CertificatesCurrent
May 2023
- RFC 9191Handling Large Certificates and Long Certificate Chains in TLS-Based EAP MethodsCurrent
February 2022
- RFC 9734X.509 Certificate Extended Key Usage (EKU) for Instant Messaging URIsCurrent
February 2025
- RFC 9763Related Certificates for Use in Multiple Authentications within a ProtocolCurrent
June 2025
- RFC 9802Use of the HSS and XMSS Hash-Based Signature Algorithms in Internet X.509 Public Key InfrastructureCurrent
June 2025
- RFC 8813Clarifications for Elliptic Curve Cryptography Subject Public Key InformationCurrent
August 2020
- RFC 9881Internet X.509 Public Key Infrastructure -- Algorithm Identifiers for the Module-Lattice-Based Digital Signature Algorithm (ML-DSA)Current
October 2025
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?