RFC 9939: PKCS #8: Private-Key Information Content Types
In plain English — editorial summary, not part of the RFC
This document defines PKCS #8 content types for use with PrivateKeyInfo and EncryptedPrivateKeyInfo as specified in RFC 5958.
Document record
- Document ID
- RFC9939
- Published
- February 2026
- Authors
- J. Mandel; R. Housley; S. Turner
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9882Use of the ML-DSA Signature Algorithm in the Cryptographic Message Syntax (CMS)Current
October 2025
- RFC 7165Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)Current
April 2014
- RFC 6664S/MIME Capabilities for Public Key DefinitionsCurrent
July 2012
- RFC 5754Using SHA2 Algorithms with Cryptographic Message SyntaxCurrent
January 2010
- RFC 3855Transporting Secure/Multipurpose Internet Mail Extensions (S/MIME) Objects in X.400Current
July 2004
- RFC 3852Cryptographic Message Syntax (CMS)Obsoleted
July 2004
- RFC 3657Use of the Camellia Encryption Algorithm in Cryptographic Message Syntax (CMS)Current
January 2004
- RFC 3565Use of the Advanced Encryption Standard (AES) Encryption Algorithm in Cryptographic Message Syntax (CMS)Current
July 2003
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?