Skip to main content

Domain-based signing and encryption using S/MIME

Document Type Expired Internet-Draft (individual in sec area)
Expired & archived
Authors William Ottaway , Alexey Melnikov
Last updated 2023-05-26 (Latest revision 2014-03-05)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Stream WG state Submitted to IESG for Publication
Document shepherd Alan Ross
Shepherd write-up Show Last changed 2014-02-12
IESG IESG state Expired (IESG: Dead)
Action Holders
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Sean Turner
Send notices to
IANA IANA review state Version Changed - Review Needed

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


The S/MIME protocols Message Specification (RFC 5751), Cryptographic Message Syntax (RFC 5652), S/MIME Certificate Handling (RFC 5750) and Enhanced Security Services for S/MIME (RFC 2634) specify a consistent way to securely send and receive MIME messages providing end to end integrity, authentication, non-repudiation and confidentiality. This document identifies a number of interoperability, technical, procedural and policy related issues that may result in end-to-end security services not being achievable. To resolve such issues, this document profiles domain-based signing and encryption using S/MIME, such as specifying how S/MIME signing and encryption can be applied between a Message Submission Agent (MSA) and a Message Delivery Agent (MDA) or between 2 Message Transfer Agents (MTA). This document is also registering 2 URI scheme: "smtp" and "submit" which are used for designating SMTP/SMTP Submission servers (respectively), as well as SMTP/Submission client accounts.


William Ottaway
Alexey Melnikov

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)