Additional New ASN.1 ModulesSoaring Hawk ConsultingPO Box 675Gold BarWA98251ietf@augustcellars.comIECA, Inc.3057 Nutley Street, Suite 106FairfaxVA22031turners@ieca.comThe Cryptographic Message Syntax (CMS) format, and many associated formats, are expressed using ASN.1. The current ASN.1 modules conform to the 1988 version of ASN.1. This document updates some auxiliary 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 change to the syntax.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 protocols still use ASN.1 from the 1988 standard, which has been deprecated. This is particularly true for the standards that relate to PKIX, CMS, and S/MIME.This document updates the following RFCs to use ASN.1 modules that conform to the 2002 version of ASN.1 .
RFC 4049, BinaryTime: An Alternate Format for Representing Date and Time in ASN.1 RFC 4073, Protecting Multiple Contents with the Cryptographic Message Syntax (CMS) RFC 5752, Multiple Signatures in Cryptographic Message Syntax (CMS) Note that some of the modules in this document get some of their definitions from places different than the modules in the original RFCs. The idea is that these modules, when combined with the modules in and can stand on their own and do not need to import definitions from anywhere else.The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in .
BinarySigningTimeModule-2009
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1)
pkcs-9(9) smime(16) modules(0) TBD-1 }
DEFINITIONS IMPLICIT TAGS ::=
BEGIN
IMPORTS
-- From PKIX-CommonTypes-2009 [I-D.ietf-pkix-new-asn1]
ATTRIBUTE
FROM PKIX-CommonTypes-2009
{ iso(1) identified-organization(3) dod(6) internet(1)
security(5) mechanisms(5) pkix(7) id-mod(0)
id-mod-pkixCommon-02(57) }
;
-- BinaryTime Definition
BinaryTime ::= INTEGER (0..MAX)
-- Signing Binary Time Attribute
aa-binarySigningTime ATTRIBUTE ::= {
TYPE BinarySigningTime
IDENTIFIED BY id-aa-binarySigningTime }
id-aa-binarySigningTime OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
smime(16) aa(2) 46 }
BinarySigningTime ::= BinaryTime
END
ContentCollectionModule-2009
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1)
pkcs-9(9) smime(16) modules(0) TBD-2 }
DEFINITIONS IMPLICIT TAGS ::=
BEGIN
IMPORTS
-- From CryptographicMessageSyntax-2009 [I-D.ietf-smime-new-asn1]
CONTENT-TYPE, Attribute, ContentInfo
FROM CryptographicMessageSyntax-2009
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1)
pkcs-9(9) smime(16) modules(0) cms-2001(14) }
;
-- Content Collection Content Type and Object Identifier
ct-ContentCollection CONTENT TYPE ::= {
ContentCollection IDENTIFIED BY id-ct-contentCollection }
id-ct-contentCollection OBJECT IDENTIFIER ::= {
iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) ct(1) 19 }
ContentCollection ::= SEQUENCE SIZE (1..MAX) OF ContentInfo
-- Content With Attributes Content Type and Object Identifier
ct-ContentWithAttributes CONTENT TYPE ::= {
{ ContentWithAttributes IDENTIFIED BY id-ct-contentWithAttrs }
id-ct-contentWithAttrs OBJECT IDENTIFIER ::= {
iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) ct(1) 20 }
ContentWithAttributes ::= SEQUENCE {
content ContentInfo,
attrs SEQUENCE SIZE (1..MAX) OF Attribute
{ ContentAttributes }
ContentAttributes ATTRIBUTE ::= { ... }
END
MultipleSignatures-2009
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
smime(16) modules(0) TBD-3 }
DEFINITIONS IMPLICIT TAGS ::=
BEGIN
-- EXPORTS All
-- The types and values defined in this module are exported for use
-- in the other ASN.1 modules. Other applications may use them for
-- their own purposes.
IMPORTS
-- Imports from PKIX-Common-Types-2009 [I-D.ietf-pkix-new-asn1]
ATTRIBUTE
FROM PKIX-CommonTypes-2009
{ iso(1) identified-organization(3) dod(6) internet(1)
security(5) mechanisms(5) pkix(7) id-mod(0)
id-mod-pkixCommon-02(57) }
-- Imports from CryptographicMessageSyntax-2009 [I-D.ietf-smime-new-asn1]
DigestAlgorithmIdentifier, SignatureAlgorithmIdentifier
FROM CryptographicMessageSyntax-2009
{ iso(1) member-body(2) us(840) rsadsi(113549)
pkcs(1) pkcs-9(9) smime(16) modules(0) id-mod-cms-2004-02(41) }
-- Imports from ExtendedSecurityServices-2009 [I-D.ietf-smime-new-asn1]
ESSCertIDv2
FROM ExtendedSecurityServices-2009
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) modules(0) id-mod-ess-2006-02(42) }
;
-- Section 3.0
at-multipleSignatures ATTRIBUTE ::= {
TYPE MultipleSignature
IDENTIFIED BY id-aa-multipleSignatures }
id-aa-multipleSignatures OBJECT IDENTIFIER ::= {
iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
id-aa(2) 51 }
MultipleSignatures ::= SEQUENCE {
bodyHashAlg DigestAlgorithmIdentifier,
signAlg SignatureAlgorithmIdentifier,
signAttrsHash SignAttrsHash,
cert ESSCertIDv2 OPTIONAL }
SignAttrsHash ::= SEQUENCE {
algID DigestAlgorithmIdentifier,
hash OCTET STRING }
END -- of MultipleSignatures-2008
This document itself does not have any security considerations. The ASN.1 modules keep the same bits-on-the-wire as the modules that they replace. None.ITU-T Recommendation X.680, X.681, X.682, and X.683ITU-T