Object Identifier Registry for the S/MIME Mail Security Working Group
RFC 7107

[Ballot comment]
There is, however, a good comment from Suresh Krishnan on his Gen-ART review. Please make sure it is handled before we pass the document to the RFC Editor.

[Ballot comment]
I have no objection but I note that according to 5226:
            The required documentation and review
            criteria for use by the Designated Expert should be provided
            when defining the registry.
This document gives the review criteria (thanks) but is silent on "documentation". Possibly silence means no documentation is needed, but it would be nice to make that explicit.

[Ballot comment]

Just minor suggestions, feel free to ignore:

- General: Maybe say that changing these OIDs would
have a bad effect on interop, since there are some
folks who don't seem to get that?

- section 3: Do you mean the expert should only
accept stuff that'd have been ok with some historical
charter for the smime wg? "Strongly related" seems
somewhat vague. Given the very broad range of
existing OIDs, what would not fit? Would some more
guidance help the expert?

IESG/Authors/WG Chairs:

IANA has reviewed draft-housley-smime-oids-00.  Authors should review
the comments and/or questions below.  Please report any inaccuracies
and respond to any questions as soon as possible.

We received the following comments/questions from the IANA's reviewer:

IANA has a question about some of the IANA actions requested in the IANA Considerations section of this document.

IANA understands that, upon approval of this document, there are fifteen actions which IANA must complete.

Of these, there are fourteen new registries - to be created in a new OID ARC defined by:

id-smime OBJECT IDENTIFIER ::= { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9) 16 }

1.2.840.113549.1.9.16

IANA Question -> Are the new registries intended to be placed in the existing SMI registry located at:

http://www.iana.org/assignments/smi-numbers/

or, shall a new standalone registry be created for the tables in this ARC?

There is one update to an existing subregistry of the Network Management Parameters registry located at:

http://www.iana.org/assignments/smi-numbers/

in the SMI Security for Mechanism Codes subregistry, a new table is to be placed below the existing one as follows:

OID Value Name Description References
--------------------- ----- --------------------- -------------
1.2.840.113549.1.9.16 smime S/MIME Mail Security [ RFC-to-be ]

The next fourteen actions will create new subregistries, in a location to be determined by the answer to the IANA Question above. Each of the registries will be managed through Expert Review as defined in RFC 5226.

First, a new subregistry will be created called the S/MIME Mail Security Registry and populated with the initial registrations as follows:

SMI Security for S/MIME Mail Security (1.2.840.113549.1.9.16)

Decimal Description References
------- -------------------------------------- -------------
0 module-identifiers [ RFC-to-be ]
1 cms-content-types [ RFC-to-be ]
2 attributes [ RFC-to-be ]
3 algorithm-identifiers [ RFC-to-be ]
4 certificate-distribution [ RFC-to-be ]
5 signature-policy-qualifiers [ RFC-to-be ]
6 commitment-type-identifiers [ RFC-to-be ]
7 test-security-policies [ RFC-to-be ]
8 symmetric-key-dist-ctrl-attrs [ RFC-to-be ]
9 signature-type-identifier [ RFC-to-be ]
10 encoded-information-types [ RFC-to-be ]
11 smime-capabilities [ RFC-to-be ]
12 pskc-attributes [ RFC-to-be ]

Second, a new subregistry will be created called the S/MIME Module Identifier Registry and populated with the initial registrations as follows:

SMI Security for S/MIME Module Identifier (1.2.840.113549.1.9.16.0)

Decimal Description References
------- -------------------------------------- ----------
1 id-mod-cms [RFC2630]
2 id-mod-ess [RFC2634]
3 id-mod-oid Reserved and Obsolete
4 id-mod-msg-v3 [RFC2633]
5 id-mod-ets-eSignature-88 [RFC3126]
6 id-mod-ets-eSignature-97 [RFC3126]
7 id-mod-ets-eSigPolicy-88 [RFC3125]
8 id-mod-ets-eSigPolicy-97 [RFC3125]
9 id-mod-certdist Reserved and Obsolete
10 id-mod-domsec [RFC3183]
11 id-mod-compress [RFC3274]
12 id-mod-symkeydist [RFC5275]
13 id-mod-cek-reuse [RFC3185]
14 id-mod-cms-2001 [RFC3369]
15 id-mod-v1AttrCert [RFC3369]
16 id-mod-cmsalg-2001 [RFC3370]
17 id-mod-cms-pwri-88 [RFC3211]
18 id-mod-cms-pwri-97 [RFC3211]
19 id-mod-cms-aes [RFC3565]
20 id-mod-cms-rsaes-oaep [RFC3560]
21 id-mod-msg-v3dot1 [RFC3851]
22 id-mod-cms-firmware-wrap [RFC4108]
23 id-mod-cms-camilla [RFC3657]
24 id-mod-cms-2004 [RFC3852]
25 id-mod-cms-seed [RFC4010]
26 id-mod-contentCollection [RFC4073]
27 id-mod-binarySigningTime [RFC4049]
28 id-mod-ets-eSignature-explicitSyntax88 [RFC5126]
29 id-mod-ets-eSignature-explicitSyntax97 [RFC5126]
30 id-mod-ess-2006 [RFC5035]
31 id-mod-cms-authEnvelopedData [RFC5083]
32 id-mod-cms-aes-ccm-and-gcm [RFC5084]
33 id-mod-symmetricKeyPkgV1 [RFC6031]
34 id-mod-multipleSig-2008 [RFC5752]
35 id-mod-timestampedData [RFC5544]
36 id-mod-symkeydist-02 [RFC5911]
37 id-mod-cmsalg-2001-02 [RFC5911]
38 id-mod-cms-aes-02 [RFC5911]
39 id-mod-msg-v3dot1-02 [RFC5911]
40 id-mod-cms-firmware-wrap-02 [RFC5911]
41 id-mod-cms-2004-02 [RFC5911]
42 id-mod-ess-2006-02 [RFC5911]
43 id-mod-cms-authEnvelopedData-02 [RFC5911]
44 id-mod-cms-aes-ccm-gcm-02 [RFC5911]
45 id-mod-cms-ecc-alg-2009-88 [RFC5753]
46 id-mod-cms-ecc-alg-2009-02 [RFC5753]
47 id-mod-aesKeyWrapWithPad-88 [RFC5649]
48 id-mod-aesKeyWrapWithPad-02 [RFC5649]
49 id-mod-MD5-XOR-EXPERIMENT [RFC6210]
50 id-mod-asymmetricKeyPkgV1 [RFC5958]
51 id-mod-encryptedKeyPkgV1 [RFC6032]
52 id-mod-cms-algorithmProtect [RFC6211]
53 id-mod-pskcAttributesModule [RFC6031]
54 id-mod-compressedDataContent [RFC6268]
55 id-mod-binSigningTime-2009 [RFC6268]
56 id-mod-contentCollect-2009 [RFC6268]
57 id-mod-cmsAuthEnvData-2009 [RFC6268]
58 id-mod-cms-2009 [RFC6268]
59 id-mod-multipleSign-2009 [RFC6268]
60 id-mod-rpkiManifest [RFC6486]
61 id-mod-rpkiROA [RFC6482]
62 id-mod-setKeyAttributeV1 [draft-herzog-setkey]
63 id-mod-keyPkgReceiptAndErrV2 [draft-housley-ct-keypackage-receipt-in-error]
64 id-mod-mts-hashsig-2013 [draft-housley-cms-mts-hash-sig]

Third, a new subregistry will be created called the S/MIME CMS Content Type Registry and populated with the initial registrations as follows:

SMI Security for S/MIME CMS Content Type (1.2.840.113549.1.9.16.1)

Decimal Description References
------- -------------------------------------- ----------
0 id-ct-anyContentType [RFC6010]
1 id-ct-receipt [RFC2634]
2 id-ct-authData [RFC2630]
3 id-ct-publishCert Reserved and Obsolete
4 id-ct-TSTInfo [RFC3161]
5 id-ct-TDTInfo Reserved and Obsolete
6 id-ct-contentInfo [RFC2630]
7 id-ct-DVCSRequestData [RFC3029]
8 id-ct-DVCSResponseData [RFC3029]
9 id-ct-compressedData [RFC3274]
10 id-ct-scvp-certValRequest [RFC5055]
11 id-ct-scvp-certValResponse [RFC5055]
12 id-ct-scvp-valPolRequest [RFC5055]
13 id-ct-scvp-valPolResponse [RFC5055]
14 id-ct-attrCertEncAttrs [RFC5755]
15 id-ct-TSReq Reserved and Obsolete
16 id-ct-firmwarePackage [RFC4108]
17 id-ct-firmwareLoadReceipt [RFC4108]
18 id-ct-firmwareLoadError [RFC4108]
19 id-ct-contentCollection [RFC4073]
20 id-ct-contentWithAttrs [RFC4073]
21 id-ct-encKeyWithID [RFC4211]
22 id-ct-encPEPSI Reserved and Obsolete
23 id-ct-authEnvelopedData [RFC5083]
24 id-ct-routeOriginAuthz [RFC6482]
25 id-ct-KP-sKeyPackage [RFC6031]
26 id-ct-rpkiManifest [RFC6486]
27 id-ct-asciiTextWithCRLF [RFC5485]
28 id-ct-xml [RFC5485]
29 id-ct-pdf [RFC5485]
30 id-ct-postscript [RFC5485]
31 id-ct-timestampedData [RFC5544]
32 id-ct-ASAdjacencyAttest Reserved and Obsolete
33 id-ct-rpkiTrustAnchor Reserved and Obsolete
34 id-ct-trustAnchorList [RFC5914]
35 id-ct-rpkiGhostbusters [RFC6493]
36 id-ct-resourceTaggedAttest Reserved and Obsolete

Fourth, a new subregistry will be created called the SMI Security for S/MIME Attributes Registry and populated with the initial registrations as follows:

SMI Security for S/MIME Attributes (1.2.840.113549.1.9.16.2)

Decimal Description References
------- -------------------------------------- ----------
1 id-aa-receiptRequest [RFC2634]
2 id-aa-securityLabel [RFC2634]
3 id-aa-mlExpandHistory [RFC2634]
4 id-aa-contentHint [RFC2634]
5 id-aa-msgSigDigest [RFC2634]
6 id-aa-encapContentType Reserved and Obsolete
7 id-aa-contentIdentifier [RFC2634]
8 id-aa-macValue Reserved and Obsolete
9 id-aa-equivalentLabels [RFC2634]
10 id-aa-contentReference [RFC2634]
11 id-aa-encrypKeyPref [RFC2634]
12 id-aa-signingCertificate [RFC2634]
13 id-aa-smimeEncryptCerts Reserved and Obsolete
14 id-aa-timeStampToken [RFC3126]
15 id-aa-ets-sigPolicyId [RFC3126]
16 id-aa-ets-commitmentType [RFC3126]
17 id-aa-ets-signerLocation [RFC3126]
18 id-aa-ets-signerAttr [RFC3126]
19 id-aa-ets-otherSigCert [RFC3126]
20 id-aa-ets-contentTimestamp [RFC3126]
21 id-aa-ets-CertificateRefs [RFC3126]
22 id-aa-ets-RevocationRefs [RFC3126]
23 id-aa-ets-certValues [RFC3126]
24 id-aa-ets-revocationValues [RFC3126]
25 id-aa-ets-escTimeStamp [RFC3126]
26 id-aa-ets-certCRLTimestamp [RFC3126]
27 id-aa-ets-archiveTimeStamp [RFC3126]
28 id-aa-signatureType [Err3757]
29 id-aa-dvcs-dvc [RFC3029]
30 id-aa-CEKReference [RFC3185]
31 id-aa-CEKMaxDecrypts [RFC3185]
32 id-aa-KEKDerivationAlg [RFC3185]
33 id-aa-intendedRecipients Reserved and Obsolete
34 id-aa-cmc-unsignedData [RFC5272]
35 id-aa-firmwarePackageID [RFC4108]
36 id-aa-targetHardwareIDs [RFC4108]
37 id-aa-decryptKeyID [RFC4108]
38 id-aa-implCryptoAlgs [RFC4108]
39 id-aa-wrappedFirmwareKey [RFC4108]
40 id-aa-communityIdentifiers [RFC4108]
41 id-aa-fwPkgMessageDigest [RFC4108]
42 id-aa-firmwarePackageInfo [RFC4108]
43 id-aa-implCompressAlgs [RFC4108]
44 id-aa-ets-attrCertificateRefs [RFC5126]
45 id-aa-ets-attrRevocationRefs [RFC5126]
46 id-aa-binarySigningTime [RFC4049]
47 id-aa-signingCertificateV2 [RFC5035]
48 id-aa-ets-archiveTimeStampV2 [RFC5126]
49 id-aa-er-internal [RFC4998]
50 id-aa-er-external [RFC4998]
51 id-aa-multipleSignatures [RFC5752]
52 id-aa-cmsAlgorithmProtect [RFC6211]
53 id-aa-setKeyInformation [draft-herzog-setkey]
54 id-aa-asymmDecryptKeyID [RFC7030]

Fifth, a new subregistry will be created called the SMI Security for S/MIME Algorithms Registry and populated with the initial registrations as follows:

SMI Security for S/MIME Algorithms (1.2.840.113549.1.9.16.3)

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 [RFC2630]
6 id-alg-CMS3DESwrap [RFC2630]
7 id-alg-CMSRC2wrap [RFC2630]
8 id-alg-zLibCompress [RFC3274]
9 id-alg-PWRI-KEK [RFC3211]
10 id-alg-SSDH [RFC3370]
11 id-alg-HMACwith3DESwrap [RFC3537]
12 id-alg-HMACwithAESwrap [RFC3537]
13 id-alg-MD5-XOR-EXPERIMENT [RFC6210]
14 id-alg-rsa-kem [RFC5990]
15 id-alg-authEnc-128 [RFC6476]
16 id-alg-authEnc-256 [RFC6476]
17 id-alg-mts-hashsig [draft-housley-cms-mts-hash-sig]

Sixth, a new subregistry will be created called the SMI Security for S/MIME Certificate Distribution Registry and populated with the initial registrations as follows:

SMI Security for S/MIME Certificate Distribution Mechanisms (1.2.840.113549.1.9.16.4)

Decimal Description References
------- -------------------------------------- ----------
1 id-cd-ldap Reserved and Obsolete

Seventh, a new subregistry will be created called the SMI Security for S/MIME Signature Policy Qualifier Registry and populated with the initial registrations as follows:

SMI Security for S/MIME Signature Policy Qualifier (1.2.840.113549.1.9.16.5)

Decimal Description References
------- -------------------------------------- ----------
1 id-spq-ets-sqt-uri [RFC3126]
2 id-spq-ets-sqt-unotice [RFC3126]

Eighth, a new subregistry will be created called the SMI Security for S/MIME Commitment Type Identifier Registry and populated with the initial registrations as follows:

SMI Security for S/MIME Commitment Type Identifier (1.2.840.113549.1.9.16.6)

Decimal Description References
------- -------------------------------------- ----------
1 id-cti-ets-proofOfOrigin [RFC3126]
2 id-cti-ets-proofOfReceipt [RFC3126]
3 id-cti-ets-proofOfDelivery [RFC3126]
4 id-cti-ets-proofOfSender [RFC3126]
5 id-cti-ets-proofOfApproval [RFC3126]
6 id-cti-ets-proofOfCreation [RFC3126]

Ninth, a new subregistry will be created called the SMI Security for S/MIME Test Security Policies Registry and populated with the initial registrations as follows:

SMI Security for S/MIME Test Security Policies (1.2.840.113549.1.9.16.7)

Decimal Description References
------- -------------------------------------- ----------
1 id-tsp-TEST-Amoco [RFC3114]
2 id-tsp-TEST-Caterpillar [RFC3114]
3 id-tsp-TEST-Whirlpool [RFC3114]
4 id-tsp-TEST-Whirlpool-Categories [RFC3114]

Tenth, a new subregistry will be created called the SMI Security for S/MIME Control Attributes for Symmetric Key Distribution Registry and populated with the initial registrations as follows:

SMI Security for S/MIME Control Attributes for Symmetric Key Distribution (1.2.840.113549.1.9.16.8)

Decimal Description References
------- -------------------------------------- ----------
1 id-skd-glUseKEK [RFC5275]
2 id-skd-glDelete [RFC5275]
3 id-skd-glAddMember [RFC5275]
4 id-skd-glDeleteMember [RFC5275]
5 id-skd-glRekey [RFC5275]
6 id-skd-glAddOwner [RFC5275]
7 id-skd-glRemoveOwner [RFC5275]
8 id-skd-glkCompromise [RFC5275]
9 id-skd-glkRefresh [RFC5275]
10 id-skd-glFailInfo Reserved and Obsolete
11 id-skd-glaQueryRequest [RFC5275]
12 id-skd-glaQueryResponse [RFC5275]
13 id-skd-glProvideCert [RFC5275]
14 id-skd-glManageCert [RFC5275]
15 id-skd-glKey [RFC5275]

Eleventh, a new subregistry will be created called the SMI Security for S/MIME Signature Type Identifiers Registry and populated with the initial registrations as follows:

SMI Security for S/MIME Signature Type Identifiers (1.2.840.113549.1.9.16.9)

Decimal Description References
------- -------------------------------------- ----------
1 id-sti-originatorSig [RFC3183]
2 id-sti-domainSig [RFC3183]
3 id-sti-addAttribSig [RFC3183]
4 id-sti-reviewSig [RFC3183]

Twelfth, a new subregistry will be created called the SMI Security for S/MIME X.400 Encoded Information Types Registry and populated with the initial registrations as follows:

SMI Security for X.400 Encoded Information Types (EIT) for S/MIME objects (1.2.840.113549.1.9.16.10)

Decimal Description References
------- -------------------------------------- ----------
1 id-eit-envelopedData [RFC3855]
2 id-eit-signedData [RFC3855]
3 id-eit-certOnly [RFC3855]
4 id-eit-signedReceipt [RFC3855]
5 id-eit-envelopedX400 [RFC3855]
6 id-eit-signedX400 [RFC3855]
7 id-eit-compressedData [RFC3855]

Thirteenth, a new subregistry will be created called the SMI Security for S/MIME Non-cryptographic Capabilities Registry and populated with the initial registrations as follows:

SMI Security for S/MIME Capabilities (other than cryptographic algorithms) (1.2.840.113549.1.9.16.11)

Decimal Description References
------- -------------------------------------- ----------
1 id-cap-preferBinaryInside [RFC3851]

Fourteenth, a new subregistry will be created called the SMI Security for S/MIME Portable Symmetric Key Container (PSKC) Attributes Registry and populated with the initial registrations as follows:

SMI Security for S/MIME Portable Symmetric Key Container (PSKC) Attributes (1.2.840.113549.1.9.16.12)

IANA Question -> is the entry for the Key Container with the description "id-pskc-moduleId" supposed to have the decimal value 7, or should it be decimal value 8?

Decimal Description References
------- -------------------------------------- ----------
1 id-pskc-manufacturer [RFC6031]
2 id-pskc-serialNo [RFC6031]
3 id-pskc-model [RFC6031]
4 id-pskc-issueNo [RFC6031]
5 id-pskc-deviceBinding [RFC6031]
6 id-pskc-deviceStartDate [RFC6031]
7 id-pskc-deviceExpiryDate [RFC6031]
7 id-pskc-moduleId [RFC6031]
9 id-pskc-keyId [RFC6031]
10 id-pskc-algorithm [RFC6031]
11 id-pskc-issuer [RFC6031]
12 id-pskc-keyProfileId [RFC6031]
13 id-pskc-keyReference [RFC6031]
14 id-pskc-friendlyName [RFC6031]
15 id-pskc-algorithmParams [RFC6031]
16 id-pskc-counter [RFC6031]
17 id-pskc-time [RFC6031]
18 id-pskc-timeInterval [RFC6031]
19 id-pskc-timeDrift [RFC6031]
20 id-pskc-valueMAC [RFC6031]
21 id-pskc-keyStartDate [RFC6031]
22 id-pskc-keyExpiryDate [RFC6031]
23 id-pskc-noOfTransactions [RFC6031]
24 id-pskc-keyUsages [RFC6031]
25 id-pskc-pinPolicy [RFC6031]
26 id-pskc-deviceUserId [RFC6031]
27 id-pskc-keyUserId [RFC6031]

IANA understands that these are the only actions required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed
until the document has been approved for publication as an RFC.
This message is only to confirm what actions will be performed.

The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce , smime@ietf.org, saag@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Object Identifier Registry for the S/MIME Mail Security Working Group) to Informational RFC


The IESG has received a request from an individual submitter to consider
the following document:
- 'Object Identifier Registry for the S/MIME Mail Security Working Group'
  as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2013-11-18. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

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, it transfers control of that arc
  to IANA, and it establishes IANA allocation policies for any future
  assignments within that arc.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-housley-smime-oids/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-housley-smime-oids/ballot/


No IPR declarations have been submitted directly on this I-D.