RFC 3183: Domain Security Services using S/MIME
In plain English — editorial summary, not part of the RFC
This document describes how the S/MIME (Secure/Multipurpose Internet Mail Extensions) protocol can be processed and generated by a number of components of a communication system, such as message transfer agents, guards and gateways to deliver security services. These services are collectively referred to as 'Domain Security Services'. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC3183
- Published
- October 2001
- Authors
- T. Dean; W. Ottaway
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- sec
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2633S/MIME Version 3 Message SpecificationObsoleted
June 1999
- RFC 2632S/MIME Version 3 Certificate HandlingObsoleted
June 1999
- RFC 5750Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate HandlingObsoleted
January 2010
- RFC 5751Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message SpecificationObsoleted
January 2010
- RFC 3250Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type RegistrationObsoleted
September 2002
- RFC 2936HTTP MIME Type Handler DetectionCurrent
September 2000
- RFC 2927MIME Directory Profile for LDAP SchemaCurrent
September 2000
- RFC 2778A Model for Presence and Instant MessagingCurrent
February 2000
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?