7107
INFORMATIONAL
Object Identifier Registry for the S/MIME Mail Security Working Group
Authors: R. Housley
Date: January 2014
Working Group: NON WORKING GROUP
Stream: IETF
Abstract
When the S/MIME Mail Security Working Group was chartered, an object identifier arc was donated by RSA Data Security for use by that working group. This document describes the object identifiers that were assigned in that donated arc, transfers control of that arc to IANA, and establishes IANA allocation policies for any future assignments within that arc.
RFC 7107
INFORMATIONAL
Internet Engineering Task Force (IETF) R. Housley
Request for Comments: 7107 Vigil Security
Category: Informational January 2014
ISSN: 2070-1721
<span class="h1">Object Identifier Registry for the S/MIME Mail Security Working Group</span>
Abstract
When the S/MIME Mail Security Working Group was chartered, an object
identifier arc was donated by RSA Data Security for use by that
working group. This document describes the object identifiers that
were assigned in that donated arc, transfers control of that arc to
IANA, and establishes IANA allocation policies for any future
assignments within that arc.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc7107">http://www.rfc-editor.org/info/rfc7107</a>.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Housley Informational [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc7107">RFC 7107</a> S/MIME OID Registry January 2014</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Subordinate Object Identifier Arcs ..............................<a href="#page-3">3</a>
<a href="#section-3">3</a>. IANA Considerations .............................................<a href="#page-4">4</a>
<a href="#section-3.1">3.1</a>. Update to "SMI Security for Mechanism Codes" Registry ......<a href="#page-4">4</a>
<a href="#section-3.2">3.2</a>. "SMI Security for S/MIME Mail Security" Registry ...........<a href="#page-4">4</a>
<a href="#section-3.3">3.3</a>. "SMI Security for S/MIME Module Identifier" Registry .......<a href="#page-5">5</a>
<a href="#section-3.4">3.4</a>. "SMI Security for S/MIME CMS Content Type" Registry ........<a href="#page-6">6</a>
<a href="#section-3.5">3.5</a>. "SMI Security for S/MIME Attributes" Registry ..............<a href="#page-7">7</a>
<a href="#section-3.6">3.6</a>. "SMI Security for S/MIME Algorithms" Registry ..............<a href="#page-9">9</a>
3.7. "SMI Security for S/MIME Certificate Distribution
Mechanisms" Registry .......................................<a href="#page-9">9</a>
3.8. "SMI Security for S/MIME Signature Policy
Qualifier" Registry .......................................<a href="#page-10">10</a>
3.9. "SMI Security for S/MIME Commitment Type
Identifier" Registry ......................................<a href="#page-10">10</a>
3.10. "SMI Security for S/MIME Test Security Policies"
Registry .................................................<a href="#page-10">10</a>
3.11. "SMI Security for S/MIME Control Attributes for
Symmetric Key Distribution" Registry .....................<a href="#page-11">11</a>
3.12. "SMI Security for S/MIME Signature Type
Identifiers" Registry ....................................<a href="#page-11">11</a>
3.13. "SMI Security for S/MIME X.400 Encoded Information
Types (EIT) for S/MIME objects" Registry .................<a href="#page-12">12</a>
3.14. "SMI Security for S/MIME Capabilities (other than
cryptographic algorithms)" Registry ......................<a href="#page-12">12</a>
3.15. "SMI Security for S/MIME Portable Symmetric Key
Container (PSKC) Attributes" Registry ....................<a href="#page-12">12</a>
<a href="#section-4">4</a>. Security Considerations ........................................<a href="#page-13">13</a>
<a href="#section-5">5</a>. References .....................................................<a href="#page-13">13</a>
<a href="#section-5.1">5.1</a>. Normative References ......................................<a href="#page-13">13</a>
<a href="#section-5.2">5.2</a>. Informative References ....................................<a href="#page-14">14</a>
<a href="#section-6">6</a>. Acknowledgements ...............................................<a href="#page-18">18</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
When the S/MIME Mail Security Working Group was chartered, an object
identifier arc was donated by RSA Data Security for use by that
working group. These object identifiers are primarily used with
Abstract Syntax Notation One (ASN.1) [<a href="#ref-ASN1-88" title=""Specification of Abstract Syntax Notation One (ASN.1)"">ASN1-88</a>] [<a href="#ref-ASN1-08" title=""Abstract Syntax Notation One (ASN.1): Specification of basic notation"">ASN1-08</a>]. The ASN.1
specifications continue to evolve, but object identifiers can be used
with any and all versions of ASN.1.
The S/MIME object identifier arc is:
id-smime OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840) rsadsi(113549) pkcs(1) pkcs9(9) 16 }
<span class="grey">Housley Informational [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc7107">RFC 7107</a> S/MIME OID Registry January 2014</span>
This document describes the object identifiers that were assigned in
that donated arc, transfers control of that arc to IANA, and
establishes IANA allocation policies for any future assignments
within that arc.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Subordinate Object Identifier Arcs</span>
Thirteen subordinate object identifier arcs were used, numbered from
zero to twelve. They were assigned as follows:
-- ASN.1 modules
id-mod OBJECT IDENTIFIER ::= { id-smime 0 }
-- Cryptographic Message Syntax (CMS) content types
id-ct OBJECT IDENTIFIER ::= { id-smime 1 }
-- attributes
id-aa OBJECT IDENTIFIER ::= { id-smime 2 }
-- algorithm identifiers
id-alg OBJECT IDENTIFIER ::= { id-smime 3 }
-- certificate distribution
id-cd OBJECT IDENTIFIER ::= { id-smime 4 }
-- signature policy qualifier
id-spq OBJECT IDENTIFIER ::= { id-smime 5 }
-- commitment type identifier
id-cti OBJECT IDENTIFIER ::= { id-smime 6 }
-- test security policies
id-tsp OBJECT IDENTIFIER ::= { id-smime 7 }
-- symmetric key distribution control attributes
id-skd OBJECT IDENTIFIER ::= { id-smime 8 }
-- signature type identifier
id-sti OBJECT IDENTIFIER ::= { id-smime 9 }
-- encoded information types
id-eit OBJECT IDENTIFIER ::= { id-smime 10 }
-- S/MIME capabilities
id-cap OBJECT IDENTIFIER ::= { id-smime 11 }
-- PSKC attributes
id-pskc OBJECT IDENTIFIER ::= { id-smime 12 }
<span class="grey">Housley Informational [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc7107">RFC 7107</a> S/MIME OID Registry January 2014</span>
The values assigned in each of these subordinate object identifier
arcs are discussed in the next section.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IANA Considerations</span>
IANA is asked to update one registry table and create fourteen
additional tables.
Updates to the new tables require both Specification Required and
Expert Review as defined in [<a href="./rfc5226" title="">RFC5226</a>]. The expert is expected to
ensure that any new values are strongly related to the work that was
done by the S/MIME Mail Security Working Group; examples include
content types, attributes, and identifiers for algorithms used with
S/MIME and CMS. Object identifiers for other purposes should not be
assigned in this arc.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Update to "SMI Security for Mechanism Codes" Registry</span>
The "SMI Security for Mechanism Codes" table generally contains
entries with a positive integer value, but the value donated by RSA
Data Security cannot be described in this manner. An accompanying
table is needed with this entry:
OID Value Name Description References
--------------------- ----- --------------------- ----------
1.2.840.113549.1.9.16 smime S/MIME Mail Security This RFC
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. "SMI Security for S/MIME Mail Security" Registry</span>
Within the SMI-numbers registry, add an "SMI Security for S/MIME Mail
Security (1.2.840.113549.1.9.16)" table with three columns:
Decimal Description References
------- -------------------------------------- ----------
0 Module identifiers This <a href="./rfc1">RFC</a>
<a href="./rfc1">1</a> CMS content types This <a href="./rfc2">RFC</a>
<a href="./rfc2">2</a> Attributes This <a href="./rfc3">RFC</a>
<a href="./rfc3">3</a> Algorithm identifiers This <a href="./rfc4">RFC</a>
<a href="./rfc4">4</a> Certificate distribution This <a href="./rfc5">RFC</a>
<a href="./rfc5">5</a> Signature policy qualifiers This <a href="./rfc6">RFC</a>
<a href="./rfc6">6</a> Commitment type identifiers This <a href="./rfc7">RFC</a>
<a href="./rfc7">7</a> Test security policies This <a href="./rfc8">RFC</a>
<a href="./rfc8">8</a> Symmetric key dist ctrl attrs This <a href="./rfc9">RFC</a>
<a href="./rfc9">9</a> Signature type identifiers This <a href="./rfc10">RFC</a>
<a href="./rfc10">10</a> Encoded information types This <a href="./rfc11">RFC</a>
<a href="./rfc11">11</a> S/MIME capabilities This <a href="./rfc12">RFC</a>
<a href="./rfc12">12</a> PSKC attributes This RFC
<span class="grey">Housley Informational [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc7107">RFC 7107</a> S/MIME OID Registry January 2014</span>
Future updates to this table require both Specification Required and
Expert Review as defined in [<a href="./rfc5226" title="">RFC5226</a>].
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. "SMI Security for S/MIME Module Identifier" Registry</span>
Within the SMI-numbers registry, add an "SMI Security for S/MIME
Module Identifier (1.2.840.113549.1.9.16.0)" table with three
columns:
Decimal Description References
------- -------------------------------------- ----------
1 id-mod-cms [<a href="./rfc2630" title=""Cryptographic Message Syntax"">RFC2630</a>]
2 id-mod-ess [<a href="./rfc2634" title=""Enhanced Security Services for S/MIME"">RFC2634</a>]
3 id-mod-oid Reserved and Obsolete
4 id-mod-msg-v3 [<a href="./rfc2633" title=""S/MIME Version 3 Message Specification"">RFC2633</a>]
5 id-mod-ets-eSignature-88 [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
6 id-mod-ets-eSignature-97 [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
7 id-mod-ets-eSigPolicy-88 [<a href="./rfc3125" title=""Electronic Signature Policies"">RFC3125</a>]
8 id-mod-ets-eSigPolicy-97 [<a href="./rfc3125" title=""Electronic Signature Policies"">RFC3125</a>]
9 id-mod-certdist Reserved and Obsolete
10 id-mod-domsec [<a href="./rfc3183" title=""Domain Security Services using S/MIME"">RFC3183</a>]
11 id-mod-compress [<a href="./rfc3274" title=""Compressed Data Content Type for Cryptographic Message Syntax (CMS)"">RFC3274</a>]
12 id-mod-symkeydist [<a href="./rfc5275" title=""CMS Symmetric Key Management and Distribution"">RFC5275</a>]
13 id-mod-cek-reuse [<a href="./rfc3185" title=""Reuse of CMS Content Encryption Keys"">RFC3185</a>]
14 id-mod-cms-2001 [<a href="./rfc3369" title=""Cryptographic Message Syntax (CMS)"">RFC3369</a>]
15 id-mod-v1AttrCert [<a href="./rfc3369" title=""Cryptographic Message Syntax (CMS)"">RFC3369</a>]
16 id-mod-cmsalg-2001 [<a href="./rfc3370" title=""Cryptographic Message Syntax (CMS) Algorithms"">RFC3370</a>]
17 id-mod-cms-pwri-88 [<a href="./rfc3211" title=""Password-based Encryption for CMS"">RFC3211</a>]
18 id-mod-cms-pwri-97 [<a href="./rfc3211" title=""Password-based Encryption for CMS"">RFC3211</a>]
19 id-mod-cms-aes [<a href="./rfc3565" title=""Use of the Advanced Encryption Standard (AES) Encryption Algorithm in Cryptographic Message Syntax (CMS)"">RFC3565</a>]
20 id-mod-cms-rsaes-oaep [<a href="./rfc3560" title=""Use of the RSAES-OAEP Key Transport Algorithm in Cryptographic Message Syntax (CMS)"">RFC3560</a>]
21 id-mod-msg-v3dot1 [<a href="./rfc3851" title=""Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification"">RFC3851</a>]
22 id-mod-cms-firmware-wrap [<a href="./rfc4108" title=""Using Cryptographic Message Syntax (CMS) to Protect Firmware Packages"">RFC4108</a>]
23 id-mod-cms-camellia [<a href="./rfc3657" title=""Use of the Camellia Encryption Algorithm in Cryptographic Message Syntax (CMS)"">RFC3657</a>]
24 id-mod-cms-2004 [<a href="./rfc3852" title=""Cryptographic Message Syntax (CMS)"">RFC3852</a>]
25 id-mod-cms-seed [<a href="#ref-Err3865" title="RFC 4010">Err3865</a>]
26 id-mod-contentCollection [<a href="./rfc4073" title=""Protecting Multiple Contents with the Cryptographic Message Syntax (CMS)"">RFC4073</a>]
27 id-mod-binarySigningTime [<a href="./rfc4049" title=""BinaryTime: An Alternate Format for Representing Date and Time in ASN.1"">RFC4049</a>]
28 id-mod-ets-eSignature-explicitSyntax88 [<a href="./rfc5126" title=""CMS Advanced Electronic Signatures (CAdES)"">RFC5126</a>]
29 id-mod-ets-eSignature-explicitSyntax97 [<a href="./rfc5126" title=""CMS Advanced Electronic Signatures (CAdES)"">RFC5126</a>]
30 id-mod-ess-2006 [<a href="./rfc5035" title=""Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility"">RFC5035</a>]
31 id-mod-cms-authEnvelopedData [<a href="./rfc5083" title=""Cryptographic Message Syntax (CMS) Authenticated-Enveloped-Data Content Type"">RFC5083</a>]
32 id-mod-cms-aes-ccm-and-gcm [<a href="./rfc5084" title=""Using AES-CCM and AES-GCM Authenticated Encryption in the Cryptographic Message Syntax (CMS)"">RFC5084</a>]
33 id-mod-symmetricKeyPkgV1 [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
34 id-mod-multipleSig-2008 [<a href="./rfc5752" title=""Multiple Signatures in Cryptographic Message Syntax (CMS)"">RFC5752</a>]
35 id-mod-timestampedData [<a href="./rfc5544" title=""Syntax for Binding Documents with Time- Stamps"">RFC5544</a>]
36 id-mod-symkeydist-02 [<a href="./rfc5911" title=""New ASN.1 Modules for Cryptographic Message Syntax (CMS) and S/MIME"">RFC5911</a>]
37 id-mod-cmsalg-2001-02 [<a href="./rfc5911" title=""New ASN.1 Modules for Cryptographic Message Syntax (CMS) and S/MIME"">RFC5911</a>]
<span class="grey">Housley Informational [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc7107">RFC 7107</a> S/MIME OID Registry January 2014</span>
38 id-mod-cms-aes-02 [<a href="./rfc5911" title=""New ASN.1 Modules for Cryptographic Message Syntax (CMS) and S/MIME"">RFC5911</a>]
39 id-mod-msg-v3dot1-02 [<a href="./rfc5911" title=""New ASN.1 Modules for Cryptographic Message Syntax (CMS) and S/MIME"">RFC5911</a>]
40 id-mod-cms-firmware-wrap-02 [<a href="./rfc5911" title=""New ASN.1 Modules for Cryptographic Message Syntax (CMS) and S/MIME"">RFC5911</a>]
41 id-mod-cms-2004-02 [<a href="./rfc5911" title=""New ASN.1 Modules for Cryptographic Message Syntax (CMS) and S/MIME"">RFC5911</a>]
42 id-mod-ess-2006-02 [<a href="./rfc5911" title=""New ASN.1 Modules for Cryptographic Message Syntax (CMS) and S/MIME"">RFC5911</a>]
43 id-mod-cms-authEnvelopedData-02 [<a href="./rfc5911" title=""New ASN.1 Modules for Cryptographic Message Syntax (CMS) and S/MIME"">RFC5911</a>]
44 id-mod-cms-aes-ccm-gcm-02 [<a href="./rfc5911" title=""New ASN.1 Modules for Cryptographic Message Syntax (CMS) and S/MIME"">RFC5911</a>]
45 id-mod-cms-ecc-alg-2009-88 [<a href="./rfc5753" title=""Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)"">RFC5753</a>]
46 id-mod-cms-ecc-alg-2009-02 [<a href="./rfc5753" title=""Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)"">RFC5753</a>]
47 id-mod-aesKeyWrapWithPad-88 [<a href="./rfc5649" title=""Advanced Encryption Standard (AES) Key Wrap with Padding Algorithm"">RFC5649</a>]
48 id-mod-aesKeyWrapWithPad-02 [<a href="./rfc5649" title=""Advanced Encryption Standard (AES) Key Wrap with Padding Algorithm"">RFC5649</a>]
49 id-mod-MD5-XOR-EXPERIMENT [<a href="#ref-Err3866" title="RFC 6210">Err3866</a>]
50 id-mod-asymmetricKeyPkgV1 [<a href="./rfc5958" title=""Asymmetric Key Packages"">RFC5958</a>]
51 id-mod-encryptedKeyPkgV1 [<a href="./rfc6032" title=""Cryptographic Message Syntax (CMS) Encrypted Key Package Content Type"">RFC6032</a>]
52 id-mod-cms-algorithmProtect [<a href="./rfc6211" title=""Cryptographic Message Syntax (CMS) Algorithm Identifier Protection Attribute"">RFC6211</a>]
53 id-mod-pskcAttributesModule [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
54 id-mod-compressedDataContent [<a href="./rfc6268" title=""Additional New ASN.1 Modules for the Cryptographic Message Syntax (CMS) and the Public Key Infrastructure Using X.509 (PKIX)"">RFC6268</a>]
55 id-mod-binSigningTime-2009 [<a href="./rfc6268" title=""Additional New ASN.1 Modules for the Cryptographic Message Syntax (CMS) and the Public Key Infrastructure Using X.509 (PKIX)"">RFC6268</a>]
56 id-mod-contentCollect-2009 [<a href="./rfc6268" title=""Additional New ASN.1 Modules for the Cryptographic Message Syntax (CMS) and the Public Key Infrastructure Using X.509 (PKIX)"">RFC6268</a>]
57 id-mod-cmsAuthEnvData-2009 [<a href="./rfc6268" title=""Additional New ASN.1 Modules for the Cryptographic Message Syntax (CMS) and the Public Key Infrastructure Using X.509 (PKIX)"">RFC6268</a>]
58 id-mod-cms-2009 [<a href="./rfc6268" title=""Additional New ASN.1 Modules for the Cryptographic Message Syntax (CMS) and the Public Key Infrastructure Using X.509 (PKIX)"">RFC6268</a>]
59 id-mod-multipleSign-2009 [<a href="./rfc6268" title=""Additional New ASN.1 Modules for the Cryptographic Message Syntax (CMS) and the Public Key Infrastructure Using X.509 (PKIX)"">RFC6268</a>]
60 id-mod-rpkiManifest [<a href="./rfc6486" title=""Manifests for the Resource Public Key Infrastructure (RPKI)"">RFC6486</a>]
61 id-mod-rpkiROA [<a href="./rfc6482" title=""A Profile for Route Origin Authorizations (ROAs)"">RFC6482</a>]
62 id-mod-setKeyAttributeV1 [<a href="#ref-SET-KEY" title=""A set-key attribute for symmetric-key packages"">SET-KEY</a>]
63 id-mod-keyPkgReceiptAndErrV2 [<a href="#ref-CMS-TYPES" title=""Cryptographic Message Syntax (CMS) Key Package Receipt and Error Content Types"">CMS-TYPES</a>]
64 id-mod-mts-hashsig-2013 [<a href="#ref-MTS-in-CMS" title=""Use of the Hash-based Merkle Tree Signature (MTS) Algorithm in the Cryptographic Message Syntax (CMS)"">MTS-in-CMS</a>]
Future updates to this table require both Specification Required and
Expert Review as defined in [<a href="./rfc5226" title="">RFC5226</a>].
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. "SMI Security for S/MIME CMS Content Type" Registry</span>
Within the SMI-numbers registry, add an "SMI Security for S/MIME CMS
Content Type (1.2.840.113549.1.9.16.1)" table with three columns:
Decimal Description References
------- -------------------------------------- ----------
0 id-ct-anyContentType [<a href="./rfc6010" title=""Cryptographic Message Syntax (CMS) Content Constraints Extension"">RFC6010</a>]
1 id-ct-receipt [<a href="./rfc2634" title=""Enhanced Security Services for S/MIME"">RFC2634</a>]
2 id-ct-authData [<a href="./rfc2630" title=""Cryptographic Message Syntax"">RFC2630</a>]
3 id-ct-publishCert Reserved and Obsolete
4 id-ct-TSTInfo [<a href="./rfc3161" title=""Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)"">RFC3161</a>]
5 id-ct-TDTInfo Reserved and Obsolete
6 id-ct-contentInfo [<a href="./rfc2630" title=""Cryptographic Message Syntax"">RFC2630</a>]
7 id-ct-DVCSRequestData [<a href="./rfc3029" title=""Internet X.509 Public Key Infrastructure Data Validation and Certification Server Protocols"">RFC3029</a>]
8 id-ct-DVCSResponseData [<a href="./rfc3029" title=""Internet X.509 Public Key Infrastructure Data Validation and Certification Server Protocols"">RFC3029</a>]
9 id-ct-compressedData [<a href="./rfc3274" title=""Compressed Data Content Type for Cryptographic Message Syntax (CMS)"">RFC3274</a>]
<span class="grey">Housley Informational [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc7107">RFC 7107</a> S/MIME OID Registry January 2014</span>
10 id-ct-scvp-certValRequest [<a href="./rfc5055" title=""Server-Based Certificate Validation Protocol (SCVP)"">RFC5055</a>]
11 id-ct-scvp-certValResponse [<a href="./rfc5055" title=""Server-Based Certificate Validation Protocol (SCVP)"">RFC5055</a>]
12 id-ct-scvp-valPolRequest [<a href="./rfc5055" title=""Server-Based Certificate Validation Protocol (SCVP)"">RFC5055</a>]
13 id-ct-scvp-valPolResponse [<a href="./rfc5055" title=""Server-Based Certificate Validation Protocol (SCVP)"">RFC5055</a>]
14 id-ct-attrCertEncAttrs [<a href="./rfc5755" title=""An Internet Attribute Certificate Profile for Authorization"">RFC5755</a>]
15 id-ct-TSReq Reserved and Obsolete
16 id-ct-firmwarePackage [<a href="./rfc4108" title=""Using Cryptographic Message Syntax (CMS) to Protect Firmware Packages"">RFC4108</a>]
17 id-ct-firmwareLoadReceipt [<a href="./rfc4108" title=""Using Cryptographic Message Syntax (CMS) to Protect Firmware Packages"">RFC4108</a>]
18 id-ct-firmwareLoadError [<a href="./rfc4108" title=""Using Cryptographic Message Syntax (CMS) to Protect Firmware Packages"">RFC4108</a>]
19 id-ct-contentCollection [<a href="./rfc4073" title=""Protecting Multiple Contents with the Cryptographic Message Syntax (CMS)"">RFC4073</a>]
20 id-ct-contentWithAttrs [<a href="./rfc4073" title=""Protecting Multiple Contents with the Cryptographic Message Syntax (CMS)"">RFC4073</a>]
21 id-ct-encKeyWithID [<a href="./rfc4211" title=""Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)"">RFC4211</a>]
22 id-ct-encPEPSI Reserved and Obsolete
23 id-ct-authEnvelopedData [<a href="./rfc5083" title=""Cryptographic Message Syntax (CMS) Authenticated-Enveloped-Data Content Type"">RFC5083</a>]
24 id-ct-routeOriginAuthz [<a href="./rfc6482" title=""A Profile for Route Origin Authorizations (ROAs)"">RFC6482</a>]
25 id-ct-KP-sKeyPackage [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
26 id-ct-rpkiManifest [<a href="./rfc6486" title=""Manifests for the Resource Public Key Infrastructure (RPKI)"">RFC6486</a>]
27 id-ct-asciiTextWithCRLF [<a href="./rfc5485" title=""Digital Signatures on Internet-Draft Documents"">RFC5485</a>]
28 id-ct-xml [<a href="./rfc5485" title=""Digital Signatures on Internet-Draft Documents"">RFC5485</a>]
29 id-ct-pdf [<a href="./rfc5485" title=""Digital Signatures on Internet-Draft Documents"">RFC5485</a>]
30 id-ct-postscript [<a href="./rfc5485" title=""Digital Signatures on Internet-Draft Documents"">RFC5485</a>]
31 id-ct-timestampedData [<a href="./rfc5544" title=""Syntax for Binding Documents with Time- Stamps"">RFC5544</a>]
32 id-ct-ASAdjacencyAttest Reserved and Obsolete
33 id-ct-rpkiTrustAnchor Reserved and Obsolete
34 id-ct-trustAnchorList [<a href="./rfc5914" title=""Trust Anchor Format"">RFC5914</a>]
35 id-ct-rpkiGhostbusters [<a href="./rfc6493" title=""The Resource Public Key Infrastructure (RPKI) Ghostbusters Record"">RFC6493</a>]
36 id-ct-resourceTaggedAttest Reserved and Obsolete
Future updates to this table require both Specification Required and
Expert Review as defined in [<a href="./rfc5226" title="">RFC5226</a>].
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. "SMI Security for S/MIME Attributes" Registry</span>
Within the SMI-numbers registry, add an "SMI Security for S/MIME
Attributes (1.2.840.113549.1.9.16.2)" table with three columns:
Decimal Description References
------- -------------------------------------- ----------
1 id-aa-receiptRequest [<a href="./rfc2634" title=""Enhanced Security Services for S/MIME"">RFC2634</a>]
2 id-aa-securityLabel [<a href="./rfc2634" title=""Enhanced Security Services for S/MIME"">RFC2634</a>]
3 id-aa-mlExpandHistory [<a href="./rfc2634" title=""Enhanced Security Services for S/MIME"">RFC2634</a>]
4 id-aa-contentHint [<a href="./rfc2634" title=""Enhanced Security Services for S/MIME"">RFC2634</a>]
5 id-aa-msgSigDigest [<a href="./rfc2634" title=""Enhanced Security Services for S/MIME"">RFC2634</a>]
6 id-aa-encapContentType Reserved and Obsolete
7 id-aa-contentIdentifier [<a href="./rfc2634" title=""Enhanced Security Services for S/MIME"">RFC2634</a>]
8 id-aa-macValue Reserved and Obsolete
9 id-aa-equivalentLabels [<a href="./rfc2634" title=""Enhanced Security Services for S/MIME"">RFC2634</a>]
10 id-aa-contentReference [<a href="./rfc2634" title=""Enhanced Security Services for S/MIME"">RFC2634</a>]
<span class="grey">Housley Informational [Page 7]</span><span id="page-8" ></span>
<span class="grey"><a href="./rfc7107">RFC 7107</a> S/MIME OID Registry January 2014</span>
11 id-aa-encrypKeyPref [<a href="./rfc2633" title=""S/MIME Version 3 Message Specification"">RFC2633</a>]
12 id-aa-signingCertificate [<a href="./rfc2634" title=""Enhanced Security Services for S/MIME"">RFC2634</a>]
13 id-aa-smimeEncryptCerts Reserved and Obsolete
14 id-aa-signatureTimeStampToken [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
15 id-aa-ets-sigPolicyId [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
16 id-aa-ets-commitmentType [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
17 id-aa-ets-signerLocation [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
18 id-aa-ets-signerAttr [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
19 id-aa-ets-otherSigCert [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
20 id-aa-ets-contentTimestamp [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
21 id-aa-ets-CertificateRefs [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
22 id-aa-ets-RevocationRefs [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
23 id-aa-ets-certValues [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
24 id-aa-ets-revocationValues [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
25 id-aa-ets-escTimeStamp [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
26 id-aa-ets-certCRLTimestamp [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
27 id-aa-ets-archiveTimeStamp [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
28 id-aa-signatureType [<a href="#ref-Err3757" title="RFC 3183">Err3757</a>]
29 id-aa-dvcs-dvc [<a href="./rfc3029" title=""Internet X.509 Public Key Infrastructure Data Validation and Certification Server Protocols"">RFC3029</a>]
30 id-aa-CEKReference [<a href="./rfc3185" title=""Reuse of CMS Content Encryption Keys"">RFC3185</a>]
31 id-aa-CEKMaxDecrypts [<a href="./rfc3185" title=""Reuse of CMS Content Encryption Keys"">RFC3185</a>]
32 id-aa-KEKDerivationAlg [<a href="./rfc3185" title=""Reuse of CMS Content Encryption Keys"">RFC3185</a>]
33 id-aa-intendedRecipients Reserved and Obsolete
34 id-aa-cmc-unsignedData [<a href="./rfc5272" title=""Certificate Management over CMS (CMC)"">RFC5272</a>]
35 id-aa-firmwarePackageID [<a href="./rfc4108" title=""Using Cryptographic Message Syntax (CMS) to Protect Firmware Packages"">RFC4108</a>]
36 id-aa-targetHardwareIDs [<a href="./rfc4108" title=""Using Cryptographic Message Syntax (CMS) to Protect Firmware Packages"">RFC4108</a>]
37 id-aa-decryptKeyID [<a href="./rfc4108" title=""Using Cryptographic Message Syntax (CMS) to Protect Firmware Packages"">RFC4108</a>]
38 id-aa-implCryptoAlgs [<a href="./rfc4108" title=""Using Cryptographic Message Syntax (CMS) to Protect Firmware Packages"">RFC4108</a>]
39 id-aa-wrappedFirmwareKey [<a href="./rfc4108" title=""Using Cryptographic Message Syntax (CMS) to Protect Firmware Packages"">RFC4108</a>]
40 id-aa-communityIdentifiers [<a href="./rfc4108" title=""Using Cryptographic Message Syntax (CMS) to Protect Firmware Packages"">RFC4108</a>]
41 id-aa-fwPkgMessageDigest [<a href="./rfc4108" title=""Using Cryptographic Message Syntax (CMS) to Protect Firmware Packages"">RFC4108</a>]
42 id-aa-firmwarePackageInfo [<a href="./rfc4108" title=""Using Cryptographic Message Syntax (CMS) to Protect Firmware Packages"">RFC4108</a>]
43 id-aa-implCompressAlgs [<a href="./rfc4108" title=""Using Cryptographic Message Syntax (CMS) to Protect Firmware Packages"">RFC4108</a>]
44 id-aa-ets-attrCertificateRefs [<a href="./rfc5126" title=""CMS Advanced Electronic Signatures (CAdES)"">RFC5126</a>]
45 id-aa-ets-attrRevocationRefs [<a href="./rfc5126" title=""CMS Advanced Electronic Signatures (CAdES)"">RFC5126</a>]
46 id-aa-binarySigningTime [<a href="./rfc4049" title=""BinaryTime: An Alternate Format for Representing Date and Time in ASN.1"">RFC4049</a>]
47 id-aa-signingCertificateV2 [<a href="./rfc5035" title=""Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility"">RFC5035</a>]
48 id-aa-ets-archiveTimeStampV2 [<a href="./rfc5126" title=""CMS Advanced Electronic Signatures (CAdES)"">RFC5126</a>]
49 id-aa-er-internal [<a href="./rfc4998" title=""Evidence Record Syntax (ERS)"">RFC4998</a>]
50 id-aa-er-external [<a href="./rfc4998" title=""Evidence Record Syntax (ERS)"">RFC4998</a>]
51 id-aa-multipleSignatures [<a href="./rfc5752" title=""Multiple Signatures in Cryptographic Message Syntax (CMS)"">RFC5752</a>]
52 id-aa-cmsAlgorithmProtect [<a href="./rfc6211" title=""Cryptographic Message Syntax (CMS) Algorithm Identifier Protection Attribute"">RFC6211</a>]
53 id-aa-setKeyInformation [<a href="#ref-SET-KEY" title=""A set-key attribute for symmetric-key packages"">SET-KEY</a>]
54 id-aa-asymmDecryptKeyID [<a href="./rfc7030" title=""Enrollment over Secure Transport"">RFC7030</a>]
Future updates to this table require both Specification Required and
Expert Review as defined in [<a href="./rfc5226" title="">RFC5226</a>].
<span class="grey">Housley Informational [Page 8]</span><span id="page-9" ></span>
<span class="grey"><a href="./rfc7107">RFC 7107</a> S/MIME OID Registry January 2014</span>
<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. "SMI Security for S/MIME Algorithms" Registry</span>
Within the SMI-numbers registry, add an "SMI Security for S/MIME
Algorithms (1.2.840.113549.1.9.16.3)" table with three columns:
Decimal Description References
------- -------------------------------------- ----------
1 id-alg-ESDHwith3DES Reserved and Obsolete
2 id-alg-ESDHwithRC2 Reserved and Obsolete
3 id-alg-3DESwrap Reserved and Obsolete
4 id-alg-RC2wrap Reserved and Obsolete
5 id-alg-ESDH [<a href="./rfc2630" title=""Cryptographic Message Syntax"">RFC2630</a>]
6 id-alg-CMS3DESwrap [<a href="./rfc2630" title=""Cryptographic Message Syntax"">RFC2630</a>]
7 id-alg-CMSRC2wrap [<a href="./rfc2630" title=""Cryptographic Message Syntax"">RFC2630</a>]
8 id-alg-zLibCompress [<a href="./rfc3274" title=""Compressed Data Content Type for Cryptographic Message Syntax (CMS)"">RFC3274</a>]
9 id-alg-PWRI-KEK [<a href="./rfc3211" title=""Password-based Encryption for CMS"">RFC3211</a>]
10 id-alg-SSDH [<a href="./rfc3370" title=""Cryptographic Message Syntax (CMS) Algorithms"">RFC3370</a>]
11 id-alg-HMACwith3DESwrap [<a href="./rfc3537" title=""Wrapping a Hashed Message Authentication Code (HMAC) key with a Triple-Data Encryption Standard (DES) Key or an Advanced Encryption Standard (AES) Key"">RFC3537</a>]
12 id-alg-HMACwithAESwrap [<a href="./rfc3537" title=""Wrapping a Hashed Message Authentication Code (HMAC) key with a Triple-Data Encryption Standard (DES) Key or an Advanced Encryption Standard (AES) Key"">RFC3537</a>]
13 id-alg-MD5-XOR-EXPERIMENT [<a href="./rfc6210" title=""Experiment: Hash Functions with Parameters in the Cryptographic Message Syntax (CMS) and S/MIME"">RFC6210</a>]
14 id-alg-rsa-kem [<a href="./rfc5990" title=""Use of the RSA-KEM Key Transport Algorithm in the Cryptographic Message Syntax (CMS)"">RFC5990</a>]
15 id-alg-authEnc-128 [<a href="./rfc6476" title=""Using Message Authentication Code (MAC) Encryption in the Cryptographic Message Syntax (CMS)"">RFC6476</a>]
16 id-alg-authEnc-256 [<a href="./rfc6476" title=""Using Message Authentication Code (MAC) Encryption in the Cryptographic Message Syntax (CMS)"">RFC6476</a>]
17 id-alg-mts-hashsig [<a href="#ref-MTS-in-CMS" title=""Use of the Hash-based Merkle Tree Signature (MTS) Algorithm in the Cryptographic Message Syntax (CMS)"">MTS-in-CMS</a>]
Future updates to this table require both Specification Required and
Expert Review as defined in [<a href="./rfc5226" title="">RFC5226</a>].
<span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a>. "SMI Security for S/MIME Certificate Distribution Mechanisms"</span>
<span class="h3"> Registry</span>
Within the SMI-numbers registry, add an "SMI Security for S/MIME
Certificate Distribution Mechanisms (1.2.840.113549.1.9.16.4)" table
with three columns:
Decimal Description References
------- -------------------------------------- ----------
1 id-cd-ldap Reserved and Obsolete
Future updates to this table require both Specification Required and
Expert Review as defined in [<a href="./rfc5226" title="">RFC5226</a>].
<span class="grey">Housley Informational [Page 9]</span><span id="page-10" ></span>
<span class="grey"><a href="./rfc7107">RFC 7107</a> S/MIME OID Registry January 2014</span>
<span class="h3"><a class="selflink" id="section-3.8" href="#section-3.8">3.8</a>. "SMI Security for S/MIME Signature Policy Qualifier" Registry</span>
Within the SMI-numbers registry, add an "SMI Security for S/MIME
Signature Policy Qualifier (1.2.840.113549.1.9.16.5)" table with
three columns:
Decimal Description References
------- -------------------------------------- ----------
1 id-spq-ets-uri [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
2 id-spq-ets-unotice [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
Future updates to this table require both Specification Required and
Expert Review as defined in [<a href="./rfc5226" title="">RFC5226</a>].
<span class="h3"><a class="selflink" id="section-3.9" href="#section-3.9">3.9</a>. "SMI Security for S/MIME Commitment Type Identifier" Registry</span>
Within the SMI-numbers registry, add an "SMI Security for S/MIME
Commitment Type Identifier (1.2.840.113549.1.9.16.6)" table with
three columns:
Decimal Description References
------- -------------------------------------- ----------
1 id-cti-ets-proofOfOrigin [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
2 id-cti-ets-proofOfReceipt [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
3 id-cti-ets-proofOfDelivery [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
4 id-cti-ets-proofOfSender [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
5 id-cti-ets-proofOfApproval [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
6 id-cti-ets-proofOfCreation [<a href="./rfc3126" title=""Electronic Signature Formats for long term electronic signatures"">RFC3126</a>]
Future updates to this table require both Specification Required and
Expert Review as defined in [<a href="./rfc5226" title="">RFC5226</a>].
<span class="h3"><a class="selflink" id="section-3.10" href="#section-3.10">3.10</a>. "SMI Security for S/MIME Test Security Policies" Registry</span>
Within the SMI-numbers registry, add an "SMI Security for S/MIME Test
Security Policies (1.2.840.113549.1.9.16.7)" table with three
columns:
Decimal Description References
------- -------------------------------------- ----------
1 id-tsp-TEST-Amoco [<a href="./rfc3114" title=""Implementing Company Classification Policy with the S/MIME Security Label"">RFC3114</a>]
2 id-tsp-TEST-Caterpillar [<a href="./rfc3114" title=""Implementing Company Classification Policy with the S/MIME Security Label"">RFC3114</a>]
3 id-tsp-TEST-Whirlpool [<a href="./rfc3114" title=""Implementing Company Classification Policy with the S/MIME Security Label"">RFC3114</a>]
4 id-tsp-TEST-Whirlpool-Categories [<a href="./rfc3114" title=""Implementing Company Classification Policy with the S/MIME Security Label"">RFC3114</a>]
Future updates to this table require both Specification Required and
Expert Review as defined in [<a href="./rfc5226" title="">RFC5226</a>].
<span class="grey">Housley Informational [Page 10]</span><span id="page-11" ></span>
<span class="grey"><a href="./rfc7107">RFC 7107</a> S/MIME OID Registry January 2014</span>
<span class="h3"><a class="selflink" id="section-3.11" href="#section-3.11">3.11</a>. "SMI Security for S/MIME Control Attributes for Symmetric Key</span>
<span class="h3"> Distribution" Registry</span>
Within the SMI-numbers registry, add an "SMI Security for S/MIME
Control Attributes for Symmetric Key Distribution
(1.2.840.113549.1.9.16.8)" table with three columns:
Decimal Description References
------- -------------------------------------- ----------
1 id-skd-glUseKEK [<a href="./rfc5275" title=""CMS Symmetric Key Management and Distribution"">RFC5275</a>]
2 id-skd-glDelete [<a href="./rfc5275" title=""CMS Symmetric Key Management and Distribution"">RFC5275</a>]
3 id-skd-glAddMember [<a href="./rfc5275" title=""CMS Symmetric Key Management and Distribution"">RFC5275</a>]
4 id-skd-glDeleteMember [<a href="./rfc5275" title=""CMS Symmetric Key Management and Distribution"">RFC5275</a>]
5 id-skd-glRekey [<a href="./rfc5275" title=""CMS Symmetric Key Management and Distribution"">RFC5275</a>]
6 id-skd-glAddOwner [<a href="./rfc5275" title=""CMS Symmetric Key Management and Distribution"">RFC5275</a>]
7 id-skd-glRemoveOwner [<a href="./rfc5275" title=""CMS Symmetric Key Management and Distribution"">RFC5275</a>]
8 id-skd-glKeyCompromise [<a href="./rfc5275" title=""CMS Symmetric Key Management and Distribution"">RFC5275</a>]
9 id-skd-glkRefresh [<a href="./rfc5275" title=""CMS Symmetric Key Management and Distribution"">RFC5275</a>]
10 id-skd-glFailInfo Reserved and Obsolete
11 id-skd-glaQueryRequest [<a href="./rfc5275" title=""CMS Symmetric Key Management and Distribution"">RFC5275</a>]
12 id-skd-glaQueryResponse [<a href="./rfc5275" title=""CMS Symmetric Key Management and Distribution"">RFC5275</a>]
13 id-skd-glProvideCert [<a href="./rfc5275" title=""CMS Symmetric Key Management and Distribution"">RFC5275</a>]
14 id-skd-glManageCert [<a href="./rfc5275" title=""CMS Symmetric Key Management and Distribution"">RFC5275</a>]
15 id-skd-glKey [<a href="./rfc5275" title=""CMS Symmetric Key Management and Distribution"">RFC5275</a>]
Future updates to this table require both Specification Required and
Expert Review as defined in [<a href="./rfc5226" title="">RFC5226</a>].
<span class="h3"><a class="selflink" id="section-3.12" href="#section-3.12">3.12</a>. "SMI Security for S/MIME Signature Type Identifiers" Registry</span>
Within the SMI-numbers registry, add an "SMI Security for S/MIME
Signature Type Identifiers (1.2.840.113549.1.9.16.9)" table with
three columns:
Decimal Description References
------- -------------------------------------- ----------
1 id-sti-originatorSig [<a href="./rfc3183" title=""Domain Security Services using S/MIME"">RFC3183</a>]
2 id-sti-domainSig [<a href="./rfc3183" title=""Domain Security Services using S/MIME"">RFC3183</a>]
3 id-sti-addAttribSig [<a href="./rfc3183" title=""Domain Security Services using S/MIME"">RFC3183</a>]
4 id-sti-reviewSig [<a href="./rfc3183" title=""Domain Security Services using S/MIME"">RFC3183</a>]
Future updates to this table require both Specification Required and
Expert Review as defined in [<a href="./rfc5226" title="">RFC5226</a>].
<span class="grey">Housley Informational [Page 11]</span><span id="page-12" ></span>
<span class="grey"><a href="./rfc7107">RFC 7107</a> S/MIME OID Registry January 2014</span>
<span class="h3"><a class="selflink" id="section-3.13" href="#section-3.13">3.13</a>. "SMI Security for S/MIME X.400 Encoded Information Types (EIT)</span>
<span class="h3"> for S/MIME objects" Registry</span>
Within the SMI-numbers registry, add an "SMI Security for X.400
Encoded Information Types (EIT) for S/MIME objects
(1.2.840.113549.1.9.16.10)" table with three columns:
Decimal Description References
------- -------------------------------------- ----------
1 id-eit-envelopedData [<a href="./rfc3855" title=""Transporting Secure/Multipurpose Internet Mail Extensions (S/MIME) Objects in X.400"">RFC3855</a>]
2 id-eit-signedData [<a href="./rfc3855" title=""Transporting Secure/Multipurpose Internet Mail Extensions (S/MIME) Objects in X.400"">RFC3855</a>]
3 id-eit-certsOnly [<a href="./rfc3855" title=""Transporting Secure/Multipurpose Internet Mail Extensions (S/MIME) Objects in X.400"">RFC3855</a>]
4 id-eit-signedReceipt [<a href="./rfc3855" title=""Transporting Secure/Multipurpose Internet Mail Extensions (S/MIME) Objects in X.400"">RFC3855</a>]
5 id-eit-envelopedX400 [<a href="./rfc3855" title=""Transporting Secure/Multipurpose Internet Mail Extensions (S/MIME) Objects in X.400"">RFC3855</a>]
6 id-eit-signedX400 [<a href="./rfc3855" title=""Transporting Secure/Multipurpose Internet Mail Extensions (S/MIME) Objects in X.400"">RFC3855</a>]
7 id-eit-compressedData [<a href="./rfc3855" title=""Transporting Secure/Multipurpose Internet Mail Extensions (S/MIME) Objects in X.400"">RFC3855</a>]
Future updates to this table require both Specification Required and
Expert Review as defined in [<a href="./rfc5226" title="">RFC5226</a>].
<span class="h3"><a class="selflink" id="section-3.14" href="#section-3.14">3.14</a>. "SMI Security for S/MIME Capabilities (other than cryptographic</span>
<span class="h3"> algorithms)" Registry</span>
Within the SMI-numbers registry, add an "SMI Security for S/MIME
Capabilities (other than cryptographic algorithms)
(1.2.840.113549.1.9.16.11)" table with three columns:
Decimal Description References
------- -------------------------------------- ----------
1 id-cap-preferBinaryInside [<a href="./rfc3851" title=""Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification"">RFC3851</a>]
Future updates to this table require both Specification Required and
Expert Review as defined in [<a href="./rfc5226" title="">RFC5226</a>].
<span class="h3"><a class="selflink" id="section-3.15" href="#section-3.15">3.15</a>. "SMI Security for S/MIME Portable Symmetric Key Container (PSKC)</span>
<span class="h3"> Attributes" Registry</span>
Within the SMI-numbers registry, add an "SMI Security for S/MIME
Portable Symmetric Key Container (PSKC) Attributes
(1.2.840.113549.1.9.16.12)" table with three columns:
Decimal Description References
------- -------------------------------------- ----------
1 id-pskc-manufacturer [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
2 id-pskc-serialNo [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
3 id-pskc-model [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
4 id-pskc-issueNo [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
5 id-pskc-deviceBinding [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
<span class="grey">Housley Informational [Page 12]</span><span id="page-13" ></span>
<span class="grey"><a href="./rfc7107">RFC 7107</a> S/MIME OID Registry January 2014</span>
6 id-pskc-deviceStartDate [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
7 id-pskc-deviceExpiryDate [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
8 id-pskc-moduleId [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
9 id-pskc-keyId [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
10 id-pskc-algorithm [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
11 id-pskc-issuer [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
12 id-pskc-keyProfileId [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
13 id-pskc-keyReference [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
14 id-pskc-friendlyName [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
15 id-pskc-algorithmParams [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
16 id-pskc-counter [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
17 id-pskc-time [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
18 id-pskc-timeInterval [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
19 id-pskc-timeDrift [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
20 id-pskc-valueMAC [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
21 id-pskc-keyStartDate [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
22 id-pskc-keyExpiryDate [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
23 id-pskc-noOfTransactions [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
24 id-pskc-keyUsages [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
25 id-pskc-pinPolicy [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
26 id-pskc-deviceUserId [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
27 id-pskc-keyUserId [<a href="./rfc6031" title=""Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type"">RFC6031</a>]
Future updates to this table require both Specification Required and
Expert Review as defined in [<a href="./rfc5226" title="">RFC5226</a>].
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
This document populates an IANA registry, and it raises no new
security considerations. The protocols that specify these values
include the security considerations associated with their usage.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. References</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Normative References</span>
[<a id="ref-ASN1-08">ASN1-08</a>] International Telecommunication Union, "Abstract Syntax
Notation One (ASN.1): Specification of basic notation",
ITU-T Recommendation X.680, 2008.
[<a id="ref-ASN1-88">ASN1-88</a>] International Telephone and Telegraph Consultative
Committee, "Specification of Abstract Syntax Notation
One (ASN.1)", CCITT Recommendation X.208, 1988.
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
May 2008.
<span class="grey">Housley Informational [Page 13]</span><span id="page-14" ></span>
<span class="grey"><a href="./rfc7107">RFC 7107</a> S/MIME OID Registry January 2014</span>
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Informative References</span>
[<a id="ref-CMS-TYPES">CMS-TYPES</a>] Housley, R., "Cryptographic Message Syntax (CMS) Key
Package Receipt and Error Content Types", Work in
Progress, December 2013.
[<a id="ref-Err3757">Err3757</a>] RFC Errata, Errata ID 3757, <a href="./rfc3183">RFC 3183</a>,
<<a href="https://www.rfc-editor.org">http://www.rfc-editor.org</a>>.
[<a id="ref-Err3865">Err3865</a>] RFC Errata, Errata ID 3865, <a href="./rfc4010">RFC 4010</a>,
<<a href="https://www.rfc-editor.org">http://www.rfc-editor.org</a>>.
[<a id="ref-Err3866">Err3866</a>] RFC Errata, Errata ID 3866, <a href="./rfc6210">RFC 6210</a>,
<<a href="https://www.rfc-editor.org">http://www.rfc-editor.org</a>>.
[<a id="ref-MTS-in-CMS">MTS-in-CMS</a>] Housley, R., "Use of the Hash-based Merkle Tree
Signature (MTS) Algorithm in the Cryptographic Message
Syntax (CMS)", Work in Progress, August 2013.
[<a id="ref-RFC2630">RFC2630</a>] Housley, R., "Cryptographic Message Syntax", <a href="./rfc2630">RFC 2630</a>,
June 1999.
[<a id="ref-RFC2633">RFC2633</a>] Ramsdell, B., Ed., "S/MIME Version 3 Message
Specification", <a href="./rfc2633">RFC 2633</a>, June 1999.
[<a id="ref-RFC2634">RFC2634</a>] Hoffman, P., Ed., "Enhanced Security Services for
S/MIME", <a href="./rfc2634">RFC 2634</a>, June 1999.
[<a id="ref-RFC3029">RFC3029</a>] Adams, C., Sylvester, P., Zolotarev, M., and R.
Zuccherato, "Internet X.509 Public Key Infrastructure
Data Validation and Certification Server Protocols",
<a href="./rfc3029">RFC 3029</a>, February 2001.
[<a id="ref-RFC3114">RFC3114</a>] Nicolls, W., "Implementing Company Classification Policy
with the S/MIME Security Label", <a href="./rfc3114">RFC 3114</a>, May 2002.
[<a id="ref-RFC3125">RFC3125</a>] Ross, J., Pinkas, D., and N. Pope, "Electronic Signature
Policies", <a href="./rfc3125">RFC 3125</a>, September 2001.
[<a id="ref-RFC3126">RFC3126</a>] Pinkas, D., Ross, J., and N. Pope, "Electronic Signature
Formats for long term electronic signatures", <a href="./rfc3126">RFC 3126</a>,
September 2001.
[<a id="ref-RFC3161">RFC3161</a>] Adams, C., Cain, P., Pinkas, D., and R. Zuccherato,
"Internet X.509 Public Key Infrastructure Time-Stamp
Protocol (TSP)", <a href="./rfc3161">RFC 3161</a>, August 2001.
<span class="grey">Housley Informational [Page 14]</span><span id="page-15" ></span>
<span class="grey"><a href="./rfc7107">RFC 7107</a> S/MIME OID Registry January 2014</span>
[<a id="ref-RFC3183">RFC3183</a>] Dean, T. and W. Ottaway, "Domain Security Services using
S/MIME", <a href="./rfc3183">RFC 3183</a>, October 2001.
[<a id="ref-RFC3185">RFC3185</a>] Farrell, S. and S. Turner, "Reuse of CMS Content
Encryption Keys", <a href="./rfc3185">RFC 3185</a>, October 2001.
[<a id="ref-RFC3211">RFC3211</a>] Gutmann, P., "Password-based Encryption for CMS",
<a href="./rfc3211">RFC 3211</a>, December 2001.
[<a id="ref-RFC3274">RFC3274</a>] Gutmann, P., "Compressed Data Content Type for
Cryptographic Message Syntax (CMS)", <a href="./rfc3274">RFC 3274</a>, June
2002.
[<a id="ref-RFC3369">RFC3369</a>] Housley, R., "Cryptographic Message Syntax (CMS)",
<a href="./rfc3369">RFC 3369</a>, August 2002.
[<a id="ref-RFC3370">RFC3370</a>] Housley, R., "Cryptographic Message Syntax (CMS)
Algorithms", <a href="./rfc3370">RFC 3370</a>, August 2002.
[<a id="ref-RFC3537">RFC3537</a>] Schaad, J. and R. Housley, "Wrapping a Hashed Message
Authentication Code (HMAC) key with a Triple-Data
Encryption Standard (DES) Key or an Advanced Encryption
Standard (AES) Key", <a href="./rfc3537">RFC 3537</a>, May 2003.
[<a id="ref-RFC3560">RFC3560</a>] Housley, R., "Use of the RSAES-OAEP Key Transport
Algorithm in Cryptographic Message Syntax (CMS)",
<a href="./rfc3560">RFC 3560</a>, July 2003.
[<a id="ref-RFC3565">RFC3565</a>] Schaad, J., "Use of the Advanced Encryption Standard
(AES) Encryption Algorithm in Cryptographic Message
Syntax (CMS)", <a href="./rfc3565">RFC 3565</a>, July 2003.
[<a id="ref-RFC3657">RFC3657</a>] Moriai, S. and A. Kato, "Use of the Camellia Encryption
Algorithm in Cryptographic Message Syntax (CMS)",
<a href="./rfc3657">RFC 3657</a>, January 2004.
[<a id="ref-RFC3851">RFC3851</a>] Ramsdell, B., Ed., "Secure/Multipurpose Internet Mail
Extensions (S/MIME) Version 3.1 Message Specification",
<a href="./rfc3851">RFC 3851</a>, July 2004.
[<a id="ref-RFC3852">RFC3852</a>] Housley, R., "Cryptographic Message Syntax (CMS)",
<a href="./rfc3852">RFC 3852</a>, July 2004.
[<a id="ref-RFC3855">RFC3855</a>] Hoffman, P. and C. Bonatti, "Transporting
Secure/Multipurpose Internet Mail Extensions (S/MIME)
Objects in X.400", <a href="./rfc3855">RFC 3855</a>, July 2004.
<span class="grey">Housley Informational [Page 15]</span><span id="page-16" ></span>
<span class="grey"><a href="./rfc7107">RFC 7107</a> S/MIME OID Registry January 2014</span>
[<a id="ref-RFC4049">RFC4049</a>] Housley, R., "BinaryTime: An Alternate Format for
Representing Date and Time in ASN.1", <a href="./rfc4049">RFC 4049</a>,
April 2005.
[<a id="ref-RFC4073">RFC4073</a>] Housley, R., "Protecting Multiple Contents with the
Cryptographic Message Syntax (CMS)", <a href="./rfc4073">RFC 4073</a>, May 2005.
[<a id="ref-RFC4108">RFC4108</a>] Housley, R., "Using Cryptographic Message Syntax (CMS)
to Protect Firmware Packages", <a href="./rfc4108">RFC 4108</a>, August 2005.
[<a id="ref-RFC4211">RFC4211</a>] Schaad, J., "Internet X.509 Public Key Infrastructure
Certificate Request Message Format (CRMF)", <a href="./rfc4211">RFC 4211</a>,
September 2005.
[<a id="ref-RFC4998">RFC4998</a>] Gondrom, T., Brandner, R., and U. Pordesch, "Evidence
Record Syntax (ERS)", <a href="./rfc4998">RFC 4998</a>, August 2007.
[<a id="ref-RFC5035">RFC5035</a>] Schaad, J., "Enhanced Security Services (ESS) Update:
Adding CertID Algorithm Agility", <a href="./rfc5035">RFC 5035</a>, August 2007.
[<a id="ref-RFC5055">RFC5055</a>] Freeman, T., Housley, R., Malpani, A., Cooper, D., and
W. Polk, "Server-Based Certificate Validation Protocol
(SCVP)", <a href="./rfc5055">RFC 5055</a>, December 2007.
[<a id="ref-RFC5083">RFC5083</a>] Housley, R., "Cryptographic Message Syntax (CMS)
Authenticated-Enveloped-Data Content Type", <a href="./rfc5083">RFC 5083</a>,
November 2007.
[<a id="ref-RFC5084">RFC5084</a>] Housley, R., "Using AES-CCM and AES-GCM Authenticated
Encryption in the Cryptographic Message Syntax (CMS)",
<a href="./rfc5084">RFC 5084</a>, November 2007.
[<a id="ref-RFC5126">RFC5126</a>] Pinkas, D., Pope, N., and J. Ross, "CMS Advanced
Electronic Signatures (CAdES)", <a href="./rfc5126">RFC 5126</a>, March 2008.
[<a id="ref-RFC5272">RFC5272</a>] Schaad, J. and M. Myers, "Certificate Management over
CMS (CMC)", <a href="./rfc5272">RFC 5272</a>, June 2008.
[<a id="ref-RFC5275">RFC5275</a>] Turner, S., "CMS Symmetric Key Management and
Distribution", <a href="./rfc5275">RFC 5275</a>, June 2008.
[<a id="ref-RFC5485">RFC5485</a>] Housley, R., "Digital Signatures on Internet-Draft
Documents", <a href="./rfc5485">RFC 5485</a>, March 2009.
[<a id="ref-RFC5544">RFC5544</a>] Santoni, A., "Syntax for Binding Documents with Time-
Stamps", <a href="./rfc5544">RFC 5544</a>, February 2010.
<span class="grey">Housley Informational [Page 16]</span><span id="page-17" ></span>
<span class="grey"><a href="./rfc7107">RFC 7107</a> S/MIME OID Registry January 2014</span>
[<a id="ref-RFC5649">RFC5649</a>] Housley, R. and M. Dworkin, "Advanced Encryption
Standard (AES) Key Wrap with Padding Algorithm",
<a href="./rfc5649">RFC 5649</a>, September 2009.
[<a id="ref-RFC5752">RFC5752</a>] Turner, S. and J. Schaad, "Multiple Signatures in
Cryptographic Message Syntax (CMS)", <a href="./rfc5752">RFC 5752</a>,
January 2010.
[<a id="ref-RFC5753">RFC5753</a>] Turner, S. and D. Brown, "Use of Elliptic Curve
Cryptography (ECC) Algorithms in Cryptographic Message
Syntax (CMS)", <a href="./rfc5753">RFC 5753</a>, January 2010.
[<a id="ref-RFC5755">RFC5755</a>] Farrell, S., Housley, R., and S. Turner, "An Internet
Attribute Certificate Profile for Authorization",
<a href="./rfc5755">RFC 5755</a>, January 2010.
[<a id="ref-RFC5911">RFC5911</a>] Hoffman, P. and J. Schaad, "New ASN.1 Modules for
Cryptographic Message Syntax (CMS) and S/MIME",
<a href="./rfc5911">RFC 5911</a>, June 2010.
[<a id="ref-RFC5914">RFC5914</a>] Housley, R., Ashmore, S., and C. Wallace, "Trust Anchor
Format", <a href="./rfc5914">RFC 5914</a>, June 2010.
[<a id="ref-RFC5958">RFC5958</a>] Turner, S., "Asymmetric Key Packages", <a href="./rfc5958">RFC 5958</a>,
August 2010.
[<a id="ref-RFC5990">RFC5990</a>] Randall, J., Kaliski, B., Brainard, J., and S. Turner,
"Use of the RSA-KEM Key Transport Algorithm in the
Cryptographic Message Syntax (CMS)", <a href="./rfc5990">RFC 5990</a>,
September 2010.
[<a id="ref-RFC6010">RFC6010</a>] Housley, R., Ashmore, S., and C. Wallace, "Cryptographic
Message Syntax (CMS) Content Constraints Extension",
<a href="./rfc6010">RFC 6010</a>, September 2010.
[<a id="ref-RFC6031">RFC6031</a>] Turner, S. and R. Housley, "Cryptographic Message Syntax
(CMS) Symmetric Key Package Content Type", <a href="./rfc6031">RFC 6031</a>,
December 2010.
[<a id="ref-RFC6032">RFC6032</a>] Turner, S. and R. Housley, "Cryptographic Message Syntax
(CMS) Encrypted Key Package Content Type", <a href="./rfc6032">RFC 6032</a>,
December 2010.
[<a id="ref-RFC6210">RFC6210</a>] Schaad, J., "Experiment: Hash Functions with Parameters
in the Cryptographic Message Syntax (CMS) and S/MIME",
<a href="./rfc6210">RFC 6210</a>, April 2011.
<span class="grey">Housley Informational [Page 17]</span><span id="page-18" ></span>
<span class="grey"><a href="./rfc7107">RFC 7107</a> S/MIME OID Registry January 2014</span>
[<a id="ref-RFC6211">RFC6211</a>] Schaad, J., "Cryptographic Message Syntax (CMS)
Algorithm Identifier Protection Attribute", <a href="./rfc6211">RFC 6211</a>,
April 2011.
[<a id="ref-RFC6268">RFC6268</a>] Schaad, J. and S. Turner, "Additional New ASN.1 Modules
for the Cryptographic Message Syntax (CMS) and the
Public Key Infrastructure Using X.509 (PKIX)", <a href="./rfc6268">RFC 6268</a>,
July 2011.
[<a id="ref-RFC6476">RFC6476</a>] Gutmann, P., "Using Message Authentication Code (MAC)
Encryption in the Cryptographic Message Syntax (CMS)",
<a href="./rfc6476">RFC 6476</a>, January 2012.
[<a id="ref-RFC6482">RFC6482</a>] Lepinski, M., Kent, S., and D. Kong, "A Profile for
Route Origin Authorizations (ROAs)", <a href="./rfc6482">RFC 6482</a>, February
2012.
[<a id="ref-RFC6486">RFC6486</a>] Austein, R., Huston, G., Kent, S., and M. Lepinski,
"Manifests for the Resource Public Key Infrastructure
(RPKI)", <a href="./rfc6486">RFC 6486</a>, February 2012.
[<a id="ref-RFC6493">RFC6493</a>] Bush, R., "The Resource Public Key Infrastructure (RPKI)
Ghostbusters Record", <a href="./rfc6493">RFC 6493</a>, February 2012.
[<a id="ref-RFC7030">RFC7030</a>] Pritikin, M., Ed., Yee, P., Ed., and D. Harkins, Ed.,
"Enrollment over Secure Transport", <a href="./rfc7030">RFC 7030</a>, October
2013.
[<a id="ref-SET-KEY">SET-KEY</a>] Herzog, J. and R. Khazan, "A set-key attribute for
symmetric-key packages", Work in Progress, October 2012.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
Many thanks to Suresh Krishnan, Jim Schaad, Sean Turner, and Carl
Wallace for their careful review and comments.
Author's Address
Russ Housley
918 Spring Knoll Drive
Herndon, VA 20170
USA
EMail: [email protected]
Housley Informational [Page 18]
Annotations
Select text to annotate