RFC 1848: MIME Object Security Services
In plain English — editorial summary, not part of the RFC
This document defines MIME Object Security Services (MOSS), a protocol that uses the multipart/signed and multipart/encrypted framework [7] to apply digital signature and encryption services to MIME objects. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1848
- Published
- October 1995
- Authors
- S. Crocker; N. Freed; J. Galvin; S. Murphy
- Status
- HISTORIC
- Stream
- IETF
- Area
- sec
- Pages
- 48
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1847Security Multiparts for MIME: Multipart/Signed and Multipart/EncryptedCurrent
October 1995
- RFC 2632S/MIME Version 3 Certificate HandlingObsoleted
June 1999
- RFC 2633S/MIME Version 3 Message SpecificationObsoleted
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 1844Multimedia E-mail (MIME) User Agent ChecklistCurrent
August 1995
- RFC 1830SMTP Service Extensions for Transmission of Large and Binary MIME MessagesObsoleted
August 1995
- RFC 1867Form-based File Upload in HTMLObsoleted
November 1995
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?