draft-ietf-smime-new-asn1-04.txt   draft-ietf-smime-new-asn1-05.txt 
Network Working Group P. Hoffman Network Working Group P. Hoffman
Internet-Draft VPN Consortium Internet-Draft VPN Consortium
Intended status: Informational J. Schaad Intended status: Informational J. Schaad
Expires: October 8, 2009 Soaring Hawk Consulting Expires: October 8, 2009 Soaring Hawk Consulting
April 6, 2009 April 6, 2009
New ASN.1 Modules for CMS and S/MIME New ASN.1 Modules for CMS and S/MIME
draft-ietf-smime-new-asn1-04.txt draft-ietf-smime-new-asn1-05.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from IETF Standards Process. Without obtaining an adequate license from
skipping to change at page 2, line 24 skipping to change at page 2, line 24
formats, are expressed using ASN.1. The current ASN.1 modules formats, are expressed using ASN.1. The current ASN.1 modules
conform to the 1988 version of ASN.1. This document updates those conform to the 1988 version of ASN.1. This document updates those
ASN.1 modules to conform to the 2002 version of ASN.1. There are no ASN.1 modules to conform to the 2002 version of ASN.1. There are no
bits-on-the-wire changes to any of the formats; this is simply a bits-on-the-wire changes to any of the formats; this is simply a
change to the syntax. change to the syntax.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Design Notes . . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Design Notes . . . . . . . . . . . . . . . . . . . . . . . 4
1.2. Issues . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. ASN.1 Module AlgorithmInformation . . . . . . . . . . . . . . 4
1.2.1. Module OIDs Changing . . . . . . . . . . . . . . . . . 4
2. ASN.1 Module AlgorithmInformation . . . . . . . . . . . . . . 5
3. ASN.1 Module for RFC 3370 . . . . . . . . . . . . . . . . . . 14 3. ASN.1 Module for RFC 3370 . . . . . . . . . . . . . . . . . . 14
4. ASN.1 Module for RFC 3565 . . . . . . . . . . . . . . . . . . 20 4. ASN.1 Module for RFC 3565 . . . . . . . . . . . . . . . . . . 19
5. ASN.1 Module for RFC 3851 . . . . . . . . . . . . . . . . . . 22 5. ASN.1 Module for RFC 3851 . . . . . . . . . . . . . . . . . . 21
6. ASN.1 Module for RFC 3852 . . . . . . . . . . . . . . . . . . 24 6. ASN.1 Module for RFC 3852 . . . . . . . . . . . . . . . . . . 24
7. ASN.1 Module for RFC 4108 . . . . . . . . . . . . . . . . . . 34 7. ASN.1 Module for RFC 4108 . . . . . . . . . . . . . . . . . . 34
8. ASN.1 Module for RFC 4998 . . . . . . . . . . . . . . . . . . 40 8. ASN.1 Module for RFC 4998 . . . . . . . . . . . . . . . . . . 39
9. ASN.1 Module for RFC 5035 . . . . . . . . . . . . . . . . . . 41 9. ASN.1 Module for RFC 5035 . . . . . . . . . . . . . . . . . . 41
10. ASN.1 Module for RFC 5083 . . . . . . . . . . . . . . . . . . 48 10. ASN.1 Module for RFC 5083 . . . . . . . . . . . . . . . . . . 48
11. ASN.1 Module for RFC 5084 . . . . . . . . . . . . . . . . . . 48 11. ASN.1 Module for RFC 5084 . . . . . . . . . . . . . . . . . . 48
12. ASN.1 Module for RFC 5275 . . . . . . . . . . . . . . . . . . 50 12. ASN.1 Module for RFC 5275 . . . . . . . . . . . . . . . . . . 50
13. Security Considerations . . . . . . . . . . . . . . . . . . . 58 13. Security Considerations . . . . . . . . . . . . . . . . . . . 58
14. Normative References . . . . . . . . . . . . . . . . . . . . . 58 14. Normative References . . . . . . . . . . . . . . . . . . . . . 58
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 59 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 59
A.1. Changes between draft-hoffman-cms-new-asn1-00 and A.1. Changes between draft-hoffman-cms-new-asn1-00 and
draft-ietf-smime-new-asn1-00 . . . . . . . . . . . . . . . 59 draft-ietf-smime-new-asn1-00 . . . . . . . . . . . . . . . 59
A.2. Changes between draft-ietf-smime-new-asn1-00 and -01 . . . 60 A.2. Changes between draft-ietf-smime-new-asn1-00 and -01 . . . 60
A.3. Changes between draft-ietf-smime-new-asn1-01 and -02 . . . 60 A.3. Changes between draft-ietf-smime-new-asn1-01 and -02 . . . 60
A.4. Changes between draft-ietf-smime-new-asn1-02 and -03 . . . 60 A.4. Changes between draft-ietf-smime-new-asn1-02 and -03 . . . 60
A.5. Changes between draft-ietf-smime-new-asn1-03 and -04 . . . 60 A.5. Changes between draft-ietf-smime-new-asn1-03 and -04 . . . 60
A.6. Changes between draft-ietf-smime-new-asn1-04 and -05 . . . 60
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 60 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 60
1. Introduction 1. Introduction
Some developers would like the IETF to use the latest version of Some developers would like the IETF to use the latest version of
ASN.1 in its standards. Most of the RFCs that relate to security ASN.1 in its standards. Most of the RFCs that relate to security
protocols still use ASN.1 from the 1988 standard, which has been protocols still use ASN.1 from the 1988 standard, which has been
deprecated. This is particularly true for the standards that relate deprecated. This is particularly true for the standards that relate
to PKIX, CMS, and S/MIME. to PKIX, CMS, and S/MIME.
skipping to change at page 4, line 37 skipping to change at page 4, line 37
disambiguate between the different modules. This is done by using disambiguate between the different modules. This is done by using
both the module name (as specified in the IMPORT statement) and the both the module name (as specified in the IMPORT statement) and the
object set name. For example, in the module for RFC 5280: object set name. For example, in the module for RFC 5280:
PublicKeys FROM PKIXAlgs-2008 { 1 3 6 1 5 5 7 0 995 } PublicKeys FROM PKIXAlgs-2008 { 1 3 6 1 5 5 7 0 995 }
PublicKeys FROM PKIX1-PSS-OAEP-Algorithms { 1 3 6 1 5 5 7 33 } PublicKeys FROM PKIX1-PSS-OAEP-Algorithms { 1 3 6 1 5 5 7 33 }
PublicKeyAlgorithms PUBLIC-KEY ::= { PKIXAlgs-2008.PublicKeys, ..., PublicKeyAlgorithms PUBLIC-KEY ::= { PKIXAlgs-2008.PublicKeys, ...,
PKIX1-PSS-OAEP-Algorithms.PublicKeys } PKIX1-PSS-OAEP-Algorithms.PublicKeys }
1.2. Issues
This section will be removed before final publication.
1.2.1. Module OIDs Changing
The OIDs given in the modules in this version of the document are the
same as the OIDs from the original modules, even though some of the
modules have changed syntax. That is clearly incorrect. In a later
version of this document, we will change the OIDs for every changed
module. The WG (hopefully in coordination with the PKIX WG) needs to
determine how to do this and what the result will be.
2. ASN.1 Module AlgorithmInformation 2. ASN.1 Module AlgorithmInformation
This section contains a module that is imported by many other modules This section contains a module that is imported by many other modules
in this document. Note that this module is also given in [NEW-PKIX]. in this document. Note that this module is also given in [NEW-PKIX].
This module does not come from any existing RFC. This module does not come from any existing RFC.
AlgorithmInformation-2009 AlgorithmInformation-2009
{iso(1) identified-organization(3) dod(6) internet(1) security(5) {iso(1) identified-organization(3) dod(6) internet(1) security(5)
mechanisms(5) pkix(7) id-mod(0) mechanisms(5) pkix(7) id-mod(0)
id-mod-algorithmInformation-02(58)} id-mod-algorithmInformation-02(58)}
skipping to change at page 60, line 40 skipping to change at page 60, line 40
Changed some multi-word keywords to hypenated (such as "SMIME CAPS" Changed some multi-word keywords to hypenated (such as "SMIME CAPS"
to "SMIME-CAPS"). to "SMIME-CAPS").
Updated the reference of X.680 to X.680, X.681, X.682, and X.683. Updated the reference of X.680 to X.680, X.681, X.682, and X.683.
A.5. Changes between draft-ietf-smime-new-asn1-03 and -04 A.5. Changes between draft-ietf-smime-new-asn1-03 and -04
Changed the status of the document. Changed the status of the document.
A.6. Changes between draft-ietf-smime-new-asn1-04 and -05
Removed the "Issues" section from section 1, which should have been
done in the last draft.
Authors' Addresses Authors' Addresses
Paul Hoffman Paul Hoffman
VPN Consortium VPN Consortium
127 Segre Place 127 Segre Place
Santa Cruz, CA 95060 Santa Cruz, CA 95060
US US
Phone: 1-831-426-9827 Phone: 1-831-426-9827
Email: paul.hoffman@vpnc.org Email: paul.hoffman@vpnc.org
 End of changes. 7 change blocks. 
20 lines changed or deleted 11 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/