draft-ietf-smime-x400transport-05.txt   draft-ietf-smime-x400transport-06.txt 
S/MIME Working Group
Internet Draft Paul Hoffman, IMC Internet Draft Paul Hoffman, IMC
draft-ietf-smime-x400transport-05.txt Chris Bonatti, IECA draft-ietf-smime-x400transport-06.txt Chris Bonatti, IECA
November 1, 2002 May 1, 2003
Expires in six months Expires November 1, 2003
Transporting S/MIME Objects in X.400 Transporting S/MIME Objects in X.400
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups Force (IETF), its areas, and its working groups. Note that other groups
skipping to change at line 261 skipping to change at line 262
| | | |
| signed-receipt id-eit-signedReceipt | | signed-receipt id-eit-signedReceipt |
| SignedData Receipt | | SignedData Receipt |
| | | |
| enveloped-x400 id-eit-envelopedx400 | | enveloped-x400 id-eit-envelopedx400 |
| EnvelopedData X.400 content | | EnvelopedData X.400 content |
| | | |
| signed-x400 id-eit-signedx400 | | signed-x400 id-eit-signedx400 |
| SignedData X.400 content | | SignedData X.400 content |
| | | |
| compressed-data id-eit-compressedData |
| CompressedData RFC 3274 compression wrapper |
| |
+-----------------------------------------------------+ +-----------------------------------------------------+
Sending agents SHOULD include the appropriate S/MIME EIT OID value. Sending agents SHOULD include the appropriate S/MIME EIT OID value.
Receiving agents SHOULD recognize S/MIME OID values in the EITs field, Receiving agents SHOULD recognize S/MIME OID values in the EITs field,
and process the message appropriately according to local procedures. and process the message appropriately according to local procedures.
In order that consistency can be obtained in future S/MIME EIT In order that consistency can be obtained in future S/MIME EIT
assignments, the following guidelines should be followed when assigning assignments, the following guidelines should be followed when assigning
new EIT values. Values assigned for S/MIME EITs should correspond to new EIT values. Values assigned for S/MIME EITs should correspond to
assigned smime-type values on a one-to-one basis. The restrictions of assigned smime-type values on a one-to-one basis. The restrictions of
skipping to change at line 350 skipping to change at line 354
The signed X.400 EIT indicates that the X.400 content field contains The signed X.400 EIT indicates that the X.400 content field contains
X.400 content that has been protected by the CMS signed-data content X.400 content that has been protected by the CMS signed-data content
type in accordance with [X400WRAP]. The resulting signed X.400 CMS type in accordance with [X400WRAP]. The resulting signed X.400 CMS
content is conveyed in accordance with section 2.2. This EIT should be content is conveyed in accordance with section 2.2. This EIT should be
indicated by the following OID value: indicated by the following OID value:
id-eit-signedX400 OBJECT IDENTIFIER ::= id-eit-signedX400 OBJECT IDENTIFIER ::=
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1)
pkcs-9(9) smime(16) id-eit(10) id-eit-signedX400(6) } pkcs-9(9) smime(16) id-eit(10) id-eit-signedX400(6) }
2.5.7 Compressed Data
The compressed data EIT indicates that the X.400 content field contains
a another type that has been compressed by the compressed-data content
type in accordance with [COMPRESS]. The resulting CMS content is
conveyed in accordance with section 2.2. This EIT should be indicated by
the following OID value:
id-eit-compressedData OBJECT IDENTIFIER ::=
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1)
pkcs-9(9) smime(16) id-eit(10) id-eit-compressedData(7) }
2.6 Interaction with X.400 Elements of Service 2.6 Interaction with X.400 Elements of Service
Care should be taken in the selection of X.400 services to be used in Care should be taken in the selection of X.400 services to be used in
conjunction with CMS objects. Services affecting conversion of the conjunction with CMS objects. Services affecting conversion of the
content, expansion of Distribution Lists (DLs), and message redirection content, expansion of Distribution Lists (DLs), and message redirection
can interact badly with services provided by the "EnvelopedData" and can interact badly with services provided by the "EnvelopedData" and
"SignedData" CMS content types. "SignedData" CMS content types.
2.6.1 MTS Conversion Services 2.6.1 MTS Conversion Services
skipping to change at line 430 skipping to change at line 446
A. References A. References
A.1 Normative References A.1 Normative References
[CERT31] Ramsdell, B., Editor, "S/MIME Version 3 Certificate [CERT31] Ramsdell, B., Editor, "S/MIME Version 3 Certificate
Handling", Internet-Draft draft-ietf-smime-rfc2632bis. Handling", Internet-Draft draft-ietf-smime-rfc2632bis.
[CMS] Housley, R., "Cryptographic Message Syntax", Internet-Draft [CMS] Housley, R., "Cryptographic Message Syntax", Internet-Draft
draft-ietf-smime-rfc2630bis. draft-ietf-smime-rfc2630bis.
[COMPRESS] Gutmann, P., Editor, "Compressed Data Content Type for
Cryptographic Message Syntax (CMS)", RFC 3274, June 2002.
[ESS] Hoffman, P., Editor "Enhanced Security Services for S/MIME", [ESS] Hoffman, P., Editor "Enhanced Security Services for S/MIME",
RFC 2634, June 1999. RFC 2634, June 1999.
[MSG] Ramsdell, B., Editor "S/MIME Version 3 Message Specification", [MSG] Ramsdell, B., Editor "S/MIME Version 3 Message Specification",
Internet-Draft draft-ietf-smime-rfc2633bis. Internet-Draft draft-ietf-smime-rfc2633bis.
[X.400] ITU-T X.400 Series of Recommendations, Information technology - [X.400] ITU-T X.400 Series of Recommendations, Information technology -
Message Handling Systems (MHS). X.400: System and Service Overview; Message Handling Systems (MHS). X.400: System and Service Overview;
X.402: Overall Architecture; X.411: Message Transfer System: Abstract X.402: Overall Architecture; X.411: Message Transfer System: Abstract
Service Definition and Procedures; X.420: Interpersonal Messaging Service Definition and Procedures; X.420: Interpersonal Messaging
skipping to change at line 467 skipping to change at line 486
Internet Mail Consortium Internet Mail Consortium
127 Segre Place 127 Segre Place
Santa Cruz, CA 95060 USA Santa Cruz, CA 95060 USA
phoffman@imc.org phoffman@imc.org
Chris Bonatti Chris Bonatti
IECA, Inc. IECA, Inc.
15309 Turkey Foot Road 15309 Turkey Foot Road
Darnestown, MD 20878-3640 USA Darnestown, MD 20878-3640 USA
bonattic@ieca.com bonattic@ieca.com
draft-ietf-smime-x400transport-06.txt expires November 1, 2003.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/