Enclosed below are the announcements for the Security Multiparts in MIME
and MIME Object Security Services RFCs!
Enjoy,
Jim
--- Begin Message ---
A new Request for Comments is now available in online RFC libraries.
RFC 1847:
Title: Security Multiparts for MIME:
Multipart/Signed and Multipart/Encrypted
Author: J. Galvin, S. Murphy, S. Crocker & N. Freed
Date: October 1995
Mailbox: galvin(_at_)tis(_dot_)com, sandy(_at_)tis(_dot_)com,
crocker(_at_)cybercash(_dot_)com,
ned(_at_)innosoft(_dot_)com
Pages: 11
Characters: 23,679
Updates/Obsoletes: none
URL: ftp://ds.internic.net/rfc/rfc1847.txt
This document defines a framework within which security services may
be applied to MIME body parts. MIME, an acronym for "Multipurpose
Internet Mail Extensions", defines the format of the contents of
Internet mail messages and provides for multi-part textual and
non-textual message bodies. The new content types are subtypes of
multipart: signed and encrypted. Each will contain two body parts:
one for the protected data and one for the control information
necessary to remove the protection. The type and contents of the
control information body parts are determined by the value of the
protocol parameter of the enclosing multipart/signed or
multipart/encrypted content type, which is required to be present.
This RFC is the product of the Privacy-Enhanced Electronic Mail
Working Group of the IETF.
This is now a Proposed Standard Protocol.
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state and
status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST(_at_)CNRI(_dot_)RESTON(_dot_)VA(_dot_)US(_dot_)
Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST(_at_)ISI(_dot_)EDU(_dot_)
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info(_at_)ISI(_dot_)EDU with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info(_at_)ISI(_dot_)EDU
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to
admin(_at_)DS(_dot_)INTERNIC(_dot_)NET(_dot_) Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR(_at_)ISI(_dot_)EDU(_dot_) Please consult RFC 1543, Instructions to
RFC
Authors, for further information.
Joyce K. Reynolds
USC/Information Sciences Institute
....
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
- <ftp://ds.internic.net/rfc/rfc1847.txt>
-
--- End Message ---
--- Begin Message ---
A new Request for Comments is now available in online RFC libraries.
RFC 1848:
Title: MIME Object Security Services
Author: S. Crocker, N. Freed, J. Galvin & S. Murphy
Date: October 1995
Mailbox: crocker(_at_)cybercash(_dot_)com, galvin(_at_)tis(_dot_)com,
murphy(_at_)tis(_dot_)com, ned(_at_)innosoft(_dot_)com
Pages: 48
Characters: 95,010
Updates/Obsoletes: none
URL: ftp://ds.internic.net/rfc/rfc1848.txt
This document defines MIME Object Security Services (MOSS), a protocol
that uses the multipart/signed and multipart/encrypted framework to
apply digital signature and encryption services to MIME objects. The
services are offered through the use of end-to-end cryptography
between an originator and a recipient at the application layer.
Asymmetric (public key) cryptography is used in support of the digital
signature service and encryption key management. Symmetric (secret
key) cryptography is used in support of the encryption service. The
procedures are intended to be compatible with a wide range of public
key management approaches, including both ad hoc and certificate-based
schemes. Mechanisms are provided to support many public key
management approaches. This RFC is the product of the
Privacy-Enhanced Electronic Mail Working Group of the IETF.
This is now a Proposed Standard Protocol.
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state and
status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST(_at_)CNRI(_dot_)RESTON(_dot_)VA(_dot_)US(_dot_)
Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST(_at_)ISI(_dot_)EDU(_dot_)
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info(_at_)ISI(_dot_)EDU with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info(_at_)ISI(_dot_)EDU
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to
admin(_at_)DS(_dot_)INTERNIC(_dot_)NET(_dot_) Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR(_at_)ISI(_dot_)EDU(_dot_) Please consult RFC 1543, Instructions to
RFC
Authors, for further information.
Joyce K. Reynolds
USC/Information Sciences Institute
....
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
- <ftp://ds.internic.net/rfc/rfc1848.txt>
-
--- End Message ---
binMYdLxx2Q7i.bin
Description: application/moss-signature