Transporting Secure/Multipurpose Internet Mail Extensions (S/MIME) Objects in X.400 (RFC3855)
Original Publication Date: 2004-Jul-01
Included in the Prior Art Database: 2004-Jul-28
Internet Society Requests For Comment (RFCs)
P. Hoffman: AUTHOR [+2]
This document describes protocol options for conveying objects that have been protected using the Cryptographic Message Syntax (CMS) and Secure/Multipurpose Internet Mail Extensions (S/MIME) version 3.1 over an X.400 message transfer system.
Network Working Group P. Hoffman
Request for Comments: 3855 IMC
Category: Standards Track C. Bonatti
Transporting Secure/Multipurpose Internet Mail
Extensions (S/MIME) Objects in X.400
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 protocol options for conveying objects that
have been protected using the Cryptographic Message Syntax (CMS) and
Secure/Multipurpose Internet Mail Extensions (S/MIME) version 3.1
over an X.400 message transfer system.
The techniques described in the Cryptographic Message Syntax [CMS]
specification and message specifications can reasonably be
transported via a variety of electronic mail systems. This
specification defines the options and values necessary to enable
interoperable transport of S/MIME messages over an X.400 system.
This document describes a mechanism for using CMS objects as the
message content of X.400 messages in a native X.400 environment.
This means that gateways or other functions that expect to deal with
IPMS, such as those specified in [MIXER] and [BODYMAP], cannot do
anything with these messages. Note that cooperating S/MIME agents
must support common forms of message content in order to achieve
Definition of gateway services to support relay of CMS object between
X.400 and SMTP environments is beyond the scope of this document.
Hoffman & Bonatti Standards Track [Page 1]
RFC 3855 Transporting S/MIME Objects in X.400 July 2004
The key words "MUST", "SHALL", "REQUIRED", "SHOULD", "RECOMMENDED",
and "MAY" in this document are to be interpreted as described in BCP
14, RFC 2119 [MUSTSHOULD].
For the purposes of this document, the following definitions apply.
ASN.1: Abstract Syntax Notation One, as defined in ISO/IEC 8824.