Securing X.400 Content with Secure/Multipurpose Internet Mail Extensions (S/MIME) (RFC3854)
Original Publication Date: 2004-Jul-01
Included in the Prior Art Database: 2004-Jul-28
Internet Society Requests For Comment (RFCs)
P. Hoffman: AUTHOR [+3]
This document describes a protocol for adding cryptographic signature and encryption services to X.400 content with Secure/Multipurpose Internet Mail Extensions (S/MIME).
Network Working Group P. Hoffman
Request for Comments: 3854 IMC
Category: Standards Track C. Bonatti
Securing X.400 Content with Secure/Multipurpose Internet Mail
Status of this Memo
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.
Copyright (C) The Internet Society (2004).
This document describes a protocol for adding cryptographic signature
and encryption services to X.400 content with Secure/Multipurpose
Internet Mail Extensions (S/MIME).
The techniques described in the Cryptographic Message Syntax [CMS]
specification are general enough to support many different content
types. The [CMS] specification thus provides many options for
providing different security mechanisms. In order to ensure
interoperability of systems within the X.400 community, it is
necessary to specify the use of CMS features to protect X.400 content
(called "CMS-X.400" in this document).
1.1. Specification Overview
This document is intended to be similar to the S/MIME Version 3.1
Message Specification [MSG] except that it is tailored to the
requirements of X.400 content rather than Multipurpose Internet Mail
Hoffman, et al. Standards Track [Page 1]
RFC 3854 Securing X.400 with S/MIME July 2004
This document defines how to create an X.400 content type that has
been cryptographically enhanced according to [CMS]. In order to
create S/MIME messages carrying X.400 content, an S/MIME agent has to
follow specifications in this document, as well as the specifications
listed in [CMS]. This memo also defines new parameter values for...