RFC 9216: S/MIME Example Keys and Certificates
In plain English — editorial summary, not part of the RFC
The S/MIME development community benefits from sharing samples of signed or encrypted data. This document facilitates such collaboration by defining a small set of X.509v3 certificates and keys for use when generating such samples.
Document record
- Document ID
- RFC9216
- Published
- April 2022
- Authors
- D. K. Gillmor
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- 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 3647Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices FrameworkCurrent
November 2003
- RFC 2527Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices FrameworkObsoleted
March 1999
- RFC 5403RPCSEC_GSS Version 2Updated
February 2009
- RFC 5750Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate HandlingObsoleted
January 2010
- RFC 4303IP Encapsulating Security Payload (ESP)Current
December 2005
- RFC 4302IP Authentication HeaderCurrent
December 2005
- RFC 4211Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)Updated
September 2005
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?