draft-ietf-smime-cmskea-00.txt   draft-ietf-smime-cmskea-01.txt 
INTERNET-DRAFT John Pawling INTERNET-DRAFT John Pawling
draft-ietf-smime-cmskea-00.txt J.G. Van Dyke & Associates draft-ietf-smime-cmskea-01.txt J.G. Van Dyke & Associates
2 April 1999 21 May 1999
Expires: 2 October 1999 Expires: 21 November 1999
CMS KEA and SKIPJACK Conventions CMS KEA and SKIPJACK Conventions
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. Internet-Drafts are working provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working its working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
skipping to change at line 212 skipping to change at line 212
structure MUST be constructed for each recipient. Each structure MUST be constructed for each recipient. Each
KeyAgreeRecipientInfo structure includes a single RecipientEncryptedKey KeyAgreeRecipientInfo structure includes a single RecipientEncryptedKey
field containing the SKIPJACK CEK wrapped for the recipient. This field containing the SKIPJACK CEK wrapped for the recipient. This
option requires more overhead than the shared UKM option because the option requires more overhead than the shared UKM option because the
KeyAgreeRecipientInfo fields (i.e. version, originator, ukm, KeyAgreeRecipientInfo fields (i.e. version, originator, ukm,
keyEncryptionAlgorithm) must be repeated for each recipient. keyEncryptionAlgorithm) must be repeated for each recipient.
The next two paragraphs apply to both options. The next two paragraphs apply to both options.
The KeyAgreeRecipientInfo keyEncryptionAlgorithm algorithm field MUST The KeyAgreeRecipientInfo keyEncryptionAlgorithm algorithm field MUST
include the id-keyExchangeAlgorithm OID. The KeyAgreeRecipientInfo include the id-kEAKeyEncryptionAlgorithm OID. The KeyAgreeRecipientInfo
keyEncryptionAlgorithm parameters field MUST be the id- keyEncryptionAlgorithm parameters field MUST be the id-
fortezzaWrap80 OID indicating that the FORTEZZA 80-bit wrap function is fortezzaWrap80 OID indicating that the FORTEZZA 80-bit wrap function is
used to wrap the 80-bit SKIPJACK CEK. used to wrap the 80-bit SKIPJACK CEK.
If the originator is not already an explicit recipient, then a copy of If the originator is not already an explicit recipient, then a copy of
the SKIPJACK CEK SHOULD be wrapped for the originator and included in the SKIPJACK CEK SHOULD be wrapped for the originator and included in
the EnvelopedData. This allows the originator to decrypt the contents the EnvelopedData. This allows the originator to decrypt the contents
of the EnvelopedData. of the EnvelopedData.
4.2.1.1. SKIPJACK CEK Wrap Process Using A Shared Originator UKM Value 4.2.1.1. SKIPJACK CEK Wrap Process Using A Shared Originator UKM Value
skipping to change at line 385 skipping to change at line 385
This section describes the conventions for using KEA and SKIPJACK with This section describes the conventions for using KEA and SKIPJACK with
the CMS enveloped-data content type to support "previously distributed" the CMS enveloped-data content type to support "previously distributed"
symmetric KEKs. When a "previously distributed" symmetric KEK is used to symmetric KEKs. When a "previously distributed" symmetric KEK is used to
wrap the SKIPJACK CEK, then the RecipientInfo KEKRecipientInfo CHOICE wrap the SKIPJACK CEK, then the RecipientInfo KEKRecipientInfo CHOICE
MUST be used. The methods by which KEA is used to generate the symmetric MUST be used. The methods by which KEA is used to generate the symmetric
KEK and by which the symmetric KEK is distributed are beyond the scope of KEK and by which the symmetric KEK is distributed are beyond the scope of
this document. this document.
The KEKRecipientInfo fields MUST be populated as specified in the [CMS] The KEKRecipientInfo fields MUST be populated as specified in the [CMS]
"KEKRecipientInfo Type" section. The KEKRecipientInfo "KEKRecipientInfo Type" section. The KEKRecipientInfo
keyEncryptionAlgorithm algorithm field MUST be the id- keyEncryptionAlgorithm algorithm field MUST be the id-fortezzaWrap80 OID
keyExchangeAlgorithm OID. The KEKRecipientInfo keyEncryptionAlgorithm (with NULL parameters) indicating that the FORTEZZA 80-bit wrap function
parameters field MUST be the id-fortezzaWrap80 OID indicating that the is used to wrap the 80-bit SKIPJACK CEK. The KEKRecipientInfo
FORTEZZA 80-bit wrap function is used to wrap the 80-bit SKIPJACK CEK. encryptedKey field MUST include the SKIPJACK CEK wrapped using the
The KEKRecipientInfo encryptedKey field MUST include the SKIPJACK CEK "previously distributed" symmetric KEK as input to the FORTEZZA 80-bit
wrapped using the "previously distributed" symmetric KEK as input to the wrap function.
FORTEZZA 80-bit wrap function.
5. Encrypted-data Conventions 5. Encrypted-data Conventions
The CMS encrypted-data content type consists of an encrypted content, The CMS encrypted-data content type consists of an encrypted content,
but no recipient information. The method for conveying the SKIPJACK CEK but no recipient information. The method for conveying the SKIPJACK CEK
required to decrypt the encrypted-data encrypted content is beyond the required to decrypt the encrypted-data encrypted content is beyond the
scope of this document. Compliant software MUST meet the requirements scope of this document. Compliant software MUST meet the requirements
for constructing an encrypted-data content type stated in [CMS]. The for constructing an encrypted-data content type stated in [CMS]. The
[CMS] "Encrypted-data Content Type" section should be studied before [CMS] "Encrypted-data Content Type" section should be studied before
reading this section, because this section does not repeat the [CMS] reading this section, because this section does not repeat the [CMS]
skipping to change at line 446 skipping to change at line 445
Skipjack-Parm ::= SEQUENCE { initialization_vector OCTET STRING } Skipjack-Parm ::= SEQUENCE { initialization_vector OCTET STRING }
id-keyExchangeAlgorithm OBJECT IDENTIFIER ::= {joint-iso-ccitt(2) id-keyExchangeAlgorithm OBJECT IDENTIFIER ::= {joint-iso-ccitt(2)
country(16) us(840) organization(1) gov(101) dod(2) infosec(1) country(16) us(840) organization(1) gov(101) dod(2) infosec(1)
algorithms(1) keyExchangeAlgorithm (22)} algorithms(1) keyExchangeAlgorithm (22)}
id-fortezzaWrap80 OBJECT IDENTIFIER ::= {joint-iso-ccitt(2) country(16) id-fortezzaWrap80 OBJECT IDENTIFIER ::= {joint-iso-ccitt(2) country(16)
us(840) organization(1) gov(101) dod(2) infosec(1) algorithms(1) us(840) organization(1) gov(101) dod(2) infosec(1) algorithms(1)
fortezzaWrap80Algorithm (23)} fortezzaWrap80Algorithm (23)}
id-kEAKeyEncryptionAlgorithm OBJECT IDENTIFIER ::= {joint-iso-ccitt(2)
country(16) us(840) organization(1) gov(101) dod(2) infosec(1)
algorithms(1) kEAKeyEncryptionAlgorithm (24)}
A. References A. References
[CMS] "Cryptographic Message Syntax", Internet Draft, draft-ietf-smime- [CMS] "Cryptographic Message Syntax", Internet Draft, draft-ietf-smime-
cms-11.txt. cms-13.txt.
[KEA] "Representation of Key Exchange Algorithm (KEA) Keys in Internet [KEA] "Representation of Key Exchange Algorithm (KEA) Keys in Internet
X.509 Public Key Infrastructure Certificates", RFC 2528. X.509 Public Key Infrastructure Certificates", RFC 2528.
[INFO] Registry of INFOSEC Technical Objects, 17 September 1998 [INFO] Registry of INFOSEC Technical Objects, 14 April 1999
[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.
[SJ-KEA] SKIPJACK and KEA Algorithm Specifications, Version 2.0, [SJ-KEA] SKIPJACK and KEA Algorithm Specifications, Version 2.0,
http://csrc.nist.gov/encryption/skipjack-kea.htm. http://csrc.nist.gov/encryption/skipjack-kea.htm.
B. Acknowledgments B. Acknowledgments
The following people have made significant contributions to this draft: The following people have made significant contributions to this draft:
David Dalkowski, Russ Housley, Pierce Leonberger, Rich Nicholas, Bob David Dalkowski, Russ Housley, Pierce Leonberger, Rich Nicholas, Bob
Relyea and Jim Schaad. Relyea and Jim Schaad.
C. Author's Address C. Changes between CMSKEA-00 and CMSKEA-01:
1) Section 4.2.1, 4th paragraph, first sentence: Changed as follows:
OLD: The KeyAgreeRecipientInfo keyEncryptionAlgorithm algorithm field
MUST include the id-keyExchangeAlgorithm OID.
NEW: The KeyAgreeRecipientInfo keyEncryptionAlgorithm algorithm field
MUST include the id-kEAKeyEncryptionAlgorithm OID.
2) Section 4.3, 2nd paragraph, second and third sentences: Changed as
follows:
OLD: The KEKRecipientInfo keyEncryptionAlgorithm algorithm field MUST
be the id-keyExchangeAlgorithm OID. The KEKRecipientInfo
keyEncryptionAlgorithm parameters field MUST be the id-fortezzaWrap80
OID indicating that the FORTEZZA 80-bit wrap function is used to wrap
the 80-bit SKIPJACK CEK.
NEW: The KEKRecipientInfo keyEncryptionAlgorithm algorithm field MUST
be the id-fortezzaWrap80 OID (with NULL parameters) indicating that the
FORTEZZA 80-bit wrap function is used to wrap the 80-bit SKIPJACK CEK.
3) Added id-kEAKeyEncryptionAlgorithm to Section 7, Object Identifier
definitions.
4) Update [CMS] and [INFO] reference definitions.
D. Author's Address
John Pawling John Pawling
J.G. Van Dyke & Associates, Inc., a Wang Global Company J.G. Van Dyke & Associates, Inc.
141 National Business Pkwy, Suite 210 141 National Business Pkwy, Suite 210
Annapolis Junction, MD 20701 Annapolis Junction, MD 20701
jsp@jgvandyke.com jsp@jgvandyke.com
(301) 939-2739 (301) 939-2739
(410) 880-6095 (410) 880-6095
D. Full Copyright Statement E. 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
are included on all such copies and derivative works. However, this are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
 End of changes. 

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