RFC 4262: X.509 Certificate Extension for Secure/Multipurpose Internet Mail Extensions (S/MIME) Capabilities
In plain English — editorial summary, not part of the RFC
This document defines a certificate extension for inclusion of Secure/Multipurpose Internet Mail Extensions (S/MIME) Capabilities in X.509 public key certificates, as defined by RFC 3280. This certificate extension provides an optional method to indicate the cryptographic capabilities of an entity as a complement to the S/MIME Capabilities signed attribute in S/MIME messages according to RFC 3851. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4262
- Published
- December 2005
- Authors
- S. Santesson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4256Generic Message Exchange Authentication for the Secure Shell Protocol (SSH)Current
January 2006
- RFC 4255Using DNS to Securely Publish Secure Shell (SSH) Key FingerprintsCurrent
January 2006
- RFC 4254The Secure Shell (SSH) Connection ProtocolUpdated
January 2006
- RFC 4253The Secure Shell (SSH) Transport Layer ProtocolUpdated
January 2006
- RFC 4252The Secure Shell (SSH) Authentication ProtocolUpdated
January 2006
- RFC 4251The Secure Shell (SSH) Protocol ArchitectureUpdated
January 2006
- RFC 4250The Secure Shell (SSH) Protocol Assigned NumbersUpdated
January 2006
- RFC 4279Pre-Shared Key Ciphersuites for Transport Layer Security (TLS)Updated
December 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?