draft-ietf-smime-idea-05.txt   draft-ietf-smime-idea-06.txt 
Internet Draft S. Teiwes, Internet Draft S. Teiwes,
draft-ietf-smime-idea-05.txt P. Hartmann, draft-ietf-smime-idea-06.txt P. Hartmann,
June 26, 2000 D. Kuenzi August 7, 2000 D. Kuenzi
Expires in six months iT_Security AG (Ltd.) Expires in six months iT_Security AG (Ltd.)
Use of the IDEA Encryption Algorithm in CMS Use of the IDEA Encryption Algorithm in CMS
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of section 10 of RFC2026. Internet-Drafts are all provisions of section 10 of RFC2026. Internet-Drafts are
working documents of the Internet Engineering Task Force (IETF), working documents of the Internet Engineering Task Force (IETF),
its areas, and its working groups. Note that other groups may also its areas, and its working groups. Note that other groups may also
skipping to change at line 36 skipping to change at line 36
To view the entire list of current Internet-Drafts, please check the To view the entire list of current Internet-Drafts, please check the
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern
Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific
Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast).
1. Introduction 1. Introduction
This memo specifies how to incorporate IDEA (International Data This memo specifies how to incorporate IDEA (International Data
Encryption Algorithm) [IDEA] into S/MIME [SMIME2, SMIME3] as Encryption Algorithm) [IDEA] into CMS [CMS] or S/MIME [SMIME2,
an additional strong algorithm for symmetric encryption. For SMIME3] as an additional strong algorithm for symmetric encryption.
organizations who make use of IDEA for data security purposes For organizations who make use of IDEA for data security purposes
it is of high interest that IDEA is also available in S/MIME. it is of high interest that IDEA is also available in S/MIME.
The intention of this memo is to provide the OIDs and algorithms The intention of this memo is to provide the OIDs and algorithms
required that IDEA can be included in S/MIME for symmetric content required that IDEA can be included in S/MIME for symmetric content
and key encryption. and key encryption.
The general functional capabilities and preferences of S/MIME are The general functional capabilities and preferences of S/MIME are
specified by the registered list of S/MIME object identifiers (OIDs). specified by the registered list of S/MIME object identifiers (OIDs).
This list of OIDs is maintained by the Internet Mail Consortium at This list of OIDs is available from the Internet Mail Consortium at
<http://www.imc.org/ietf-smime/oids.html>. <http://www.imc.org/ietf-smime/oids.html>.
The set of S/MIME functions provided by a client is expressed by the The set of S/MIME functions provided by a client is expressed by the
S/MIME capabilities attribute. This attribute contains a list of OIDs S/MIME capabilities attribute. This attribute contains a list of OIDs
of supported cryptographic functions. of supported cryptographic functions.
This draft is being discussed on the "ietf-smime" mailing list. To
subscribe, send a message to:
ietf-smime-request@imc.org
with the single word
subscribe
in the body of the message. There is a Web site for the mailing list
at <http://www.imc.org/ietf-smime/>
In this document, the terms MUST, MUST NOT, SHOULD, and SHOULD NOT In this document, the terms MUST, MUST NOT, SHOULD, and SHOULD NOT
are used in capital letters. This conforms to the definitions in are used in capital letters. This conforms to the definitions in
[MUSTSHOULD]. [MUSTSHOULD].
2. Object Identifier for Content and Key Encryption 2. Object Identifier for Content and Key Encryption
The Cryptographic Message Syntax [CMS], derived from PKCS#7 [PKCS7], The Cryptographic Message Syntax [CMS], derived from PKCS#7 [PKCS7],
is the framework for the implementation of cryptographic functions in is the framework for the implementation of cryptographic functions in
S/MIME. It specifies data formats and encryption processes without S/MIME. It specifies data formats and encryption processes without
naming the cryptographic algorithms. Each algorithm which is used naming the cryptographic algorithms. Each algorithm which is used
skipping to change at line 95 skipping to change at line 87
mode is recommended. The key length is fixed to 128 bits. mode is recommended. The key length is fixed to 128 bits.
The IDEA content-encryption algorithm in CBC mode has the object The IDEA content-encryption algorithm in CBC mode has the object
identifier identifier
IDEA-CBC OBJECT IDENTIFIER IDEA-CBC OBJECT IDENTIFIER
::= { iso(1) identified-organization(3) ::= { iso(1) identified-organization(3)
usdod(6) oid(1) private(4) enterprises(1) usdod(6) oid(1) private(4) enterprises(1)
ascom(188) systec(7) security(1) algorithms(1) 2 } ascom(188) systec(7) security(1) algorithms(1) 2 }
The identifier's parameters field contains the initial The identifier's parameters field contains the initialization
vector IV as an optional parameter. vector (IV) as an optional parameter.
IDEA-CBCPar ::= SEQUENCE { IDEA-CBCPar ::= SEQUENCE {
IV OCTET STRING OPTIONAL -- exactly 8 octets } iv OCTET STRING OPTIONAL } -- exactly 8 octets
If IV is specified as above, it MUST be used as initial vector. In If IV is specified as above, it MUST be used as initial vector. In
this case, the ciphertext MUST NOT include the initial vector. If this case, the ciphertext MUST NOT include the initial vector. If
IV is not specified, the first 64 bits of the ciphertext MUST be IV is not specified, the first 64 bits of the ciphertext MUST be
considered as the initial vector. However, this alternative of not considered as the initial vector. However, this alternative of not
including the IV SHOULD NOT be applied in S/MIME. including the IV SHOULD NOT be applied in CMS or S/MIME.
The key-wrap/unwrap algorithms used to encrypt/decrypt an IDEA The key-wrap/unwrap algorithms used to encrypt/decrypt an IDEA
content-encryption key with an IDEA key-encryption key are content-encryption key with an IDEA key-encryption key are
specified in the following section. Generation and distribution specified in the following section. Generation and distribution
of IDEA key-encryption keys are beyond the scope of this document. of IDEA key-encryption keys are beyond the scope of this document.
The IDEA key-encryption algorithm has the object identifier The IDEA key-encryption algorithm has the object identifier
id-alg-CMSIDEAwrap OBJECT IDENTIFIER id-alg-CMSIDEAwrap OBJECT IDENTIFIER
::= { iso(1) identified-organization(3) ::= { iso(1) identified-organization(3)
skipping to change at line 229 skipping to change at line 221
[IDEA] X. Lai, "On the design and security of block ciphers", ETH [IDEA] X. Lai, "On the design and security of block ciphers", ETH
Series in Information Processing, J.L. Massey (editor), vol. 1, Series in Information Processing, J.L. Massey (editor), vol. 1,
Hartung-Gorre Verlag Konstanz, Technische Hochschule (Zurich), 1992. Hartung-Gorre Verlag Konstanz, Technische Hochschule (Zurich), 1992.
A. J. Menezes, P.C. v. Oorschot, S.A. Vanstone, "Handbook of Applied A. J. Menezes, P.C. v. Oorschot, S.A. Vanstone, "Handbook of Applied
Cryptography," CRC Press New York, 1997, p. 265. Cryptography," CRC Press New York, 1997, p. 265.
B. Schneier, "Applied Cryptography," 2nd ed., John Wiley & Sons Inc. B. Schneier, "Applied Cryptography," 2nd ed., John Wiley & Sons Inc.
New York, 1996, pp. 319-325. New York, 1996, pp. 319-325.
IPR: see the "IETF Page of Intellectual Property Rights Notices", IPR: see the "IETF Page of Intellectual Property Rights Notices",
http://www.ietf.org/ipr.html http://www.ietf.org/ipr.html
[CMS] "Cryptographic Message Syntax", RFC 2630.
[SMIME2] "S/MIME Version 2 Message Specification", RFC 2311, and [SMIME2] "S/MIME Version 2 Message Specification", RFC 2311, and
"S/MIME Version 2 Certificate Handling", RFC 2312. "S/MIME Version 2 Certificate Handling", RFC 2312.
[SMIME3] "S/MIME Version 3 Certificate Handling", RFC 2632, and [SMIME3] "S/MIME Version 3 Certificate Handling", RFC 2632, and
"S/MIME Version 3 Message Specification", RFC 2633. "S/MIME Version 3 Message Specification", RFC 2633.
[MUSTSHOULD] "Key words for use in RFCs to Indicate Requirement [MUSTSHOULD] "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119. Levels", RFC 2119.
[CMS] "Cryptographic Message Syntax", RFC 2630.
[PKCS7] "PKCS #7: Cryptographic Message Syntax Version 1.5", [PKCS7] "PKCS #7: Cryptographic Message Syntax Version 1.5",
RFC 2315. RFC 2315.
B. Comments on IDEA Security and Standards B. Comments on IDEA Security and Standards
The IDEA algorithm was developed in a joint project involving the The IDEA algorithm was developed in a joint project involving the
Swiss Federal Institute of Technology in Zurich (Dr. X. Lai and Swiss Federal Institute of Technology in Zurich (Dr. X. Lai and
Prof. J.L. Massey) and Ascom Ltd. The aim of the project was to Prof. J.L. Massey) and Ascom Ltd. The aim of the project was to
develop a strong encryption algorithm that could replace the DES develop a strong encryption algorithm that could replace the DES
algorithm. algorithm.
skipping to change at line 278 skipping to change at line 270
IDEA(TM) is protected by international copyright law and in addition IDEA(TM) is protected by international copyright law and in addition
has been patented in several countries. Because Ascom wants to make has been patented in several countries. Because Ascom wants to make
this highly secure algorithm widely available, the non-commercial use this highly secure algorithm widely available, the non-commercial use
of this algorithm is free. of this algorithm is free.
Any party wishing to know more about IDEA or to request a license Any party wishing to know more about IDEA or to request a license
should visit the web sites should visit the web sites
<http://www.media-crypt.com/>, <http://www.it-sec.com/> <http://www.media-crypt.com/>, <http://www.it-sec.com/>
or send an e-mail to or send an e-mail to
info@media-crypt.com or Idea@it-sec.com. info@media-crypt.com or info@it-sec.com.
D. Acknowledgements D. Acknowledgements
We would like to thank Jim Schaad and Francois Zeller for their We would like to thank Jim Schaad and Francois Zeller for their
contributions to this document. contributions to this document.
E. Authors' Address E. Authors' Address
iT_Security AG (Ltd.) iT_Security AG (Ltd.)
Badenerstrasse 530 Badenerstrasse 530
CH-8048 Zurich, Switzerland CH-8048 Zurich, Switzerland
Phone: +41 1 236 9900 Phone: +41 1 404 8200
Fax : +41 1 236 9990 Fax : +41 1 404 8201
Email: {stephan.teiwes,peter.hartmann,diego.kuenzi}@it-sec.com Email: {stephan.teiwes,peter.hartmann,diego.kuenzi}@it-sec.com
F. Full Copyright Statement F. Full Copyright Statement
Copyright (C) The Internet Society (date). All Rights Reserved. Copyright (C) The Internet Society (date). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph
 End of changes. 

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