Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 11
- Abstract
- This document defines a framework within which security services may be applied to MIME body parts. [STANDARDS-TRACK] This memo defines a new Simple Mail Transfer Protocol (SMTP) [1] reply code, 521, which one may use to indicate that an Internet host does not accept incoming mail. This memo defines an Experimental Protocol for the Internet community. This memo defines an extension to the SMTP service whereby an interrupted SMTP transaction can be restarted at a later time without having to repeat all of the commands and message content sent prior to the interruption. This memo defines an Experimental Protocol for the Internet community.
- Publication Date
- 1995-10-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC1847- Link
- https://doi.org/10.17487/RFC1847
- Author(s)
- James GalvinSandy MurphySteve CrockerNed Freed
- Keyword(s)
- MIME-Encyp, Mail, Multipurpose, Extensions
Latest version of IETF RFC 1847
Document Versions — IETF RFC 1847
-
▶ IETF RFC 1847 (1995-10-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- IETF RFC 822 [Superseded*]
- IETF RFC 1521 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC1847.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 1847, Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted. Available at https://doi.org/10.17487/RFC1847
Snippet:
IETF RFC 1847, Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted. Available at https://doi.org/10.17487/RFC1847
HTML (ISO 690 compliant)
Preview:
IETF RFC 1847, Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted. Available at https://doi.org/10.17487/RFC1847
Snippet:
<span class="citation"><cite>IETF RFC 1847</cite>, Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted. Available at <a href="https://doi.org/10.17487/RFC1847" target="_blank" rel="noopener">https://doi.org/10.17487/RFC1847</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 1847, Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted
doi: 10.17487/RFC1847
url: https://doi.org/10.17487/RFC1847
doi: 10.17487/RFC1847
url: https://doi.org/10.17487/RFC1847
Snippet:
<li> <cite id="bib-rfc1847">IETF RFC 1847</cite>, Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted <span class="doi">10.17487/RFC1847</span> </li>
Referenced By
- IETF RFC 1848 [Active*]
- IETF RFC 2015 [Active*]
- IETF RFC 2311 [Active*]
- IETF RFC 2316 [Active*]
- IETF RFC 2480 [Active*]
- IETF RFC 2510 [Superseded*]
- IETF RFC 2595 [Active*]
- IETF RFC 2633 [Superseded*]
- IETF RFC 2821 [Superseded*]
- IETF RFC 2975 [Active*]
- IETF RFC 3156 [Active*]
- IETF RFC 3261 [Active*]
- IETF RFC 3335 [Active*]
- IETF RFC 3631 [Active*]
- IETF RFC 3851 [Superseded*]
- IETF RFC 3862 [Active*]
- IETF RFC 3923 [Active*]
- IETF RFC 4210 [Superseded*]
- IETF RFC 4823 [Active*]
- IETF RFC 4871 [Superseded*]
- IETF RFC 5321 [Active*]
- IETF RFC 5751 [Superseded*]