< draft-housley-smime-oids-00.txt   draft-housley-smime-oids-01.txt >
INTERNET-DRAFT R. Housley INTERNET-DRAFT R. Housley
Intended Status: Informational Vigil Security Intended Status: Informational Vigil Security
Expires: 20 April 2014 20 October 2013 Expires: 1 June 2014 1 December 2013
Object Identifier Registry for the S/MIME Mail Security Working Group Object Identifier Registry for the S/MIME Mail Security Working Group
<draft-housley-smime-oids-00.txt> <draft-housley-smime-oids-01.txt>
Abstract Abstract
When the S/MIME Mail Security Working Group was chartered, an object When the S/MIME Mail Security Working Group was chartered, an object
identifier arc was donated by RSA Data Security for use by that identifier arc was donated by RSA Data Security for use by that
working group. This document describes the object identifiers that working group. This document describes the object identifiers that
were assigned in that donated arc, it transfers control of that arc were assigned in that donated arc, it transfers control of that arc
to IANA, and it establishes IANA allocation policies for any future to IANA, and it establishes IANA allocation policies for any future
assignments within that arc. assignments within that arc.
skipping to change at page 2, line 24 skipping to change at page 2, line 24
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
3.1. Update to SMI Security for Mechanism Codes Registry . . . 4 3.1. Update to SMI Security for Mechanism Codes Registry . . . 4
3.2. Add SMI Security for S/MIME Mail Security Registry . . . . 4 3.2. Add SMI Security for S/MIME Mail Security Registry . . . . 4
3.3. Add SMI Security for S/MIME Module Identifier Registry . . 5 3.3. Add SMI Security for S/MIME Module Identifier Registry . . 5
3.4. Add SMI Security for S/MIME CMS Content Type Registry . . 6 3.4. Add SMI Security for S/MIME CMS Content Type Registry . . 6
3.5. Add SMI Security for S/MIME Attributes Registry . . . . . 7 3.5. Add SMI Security for S/MIME Attributes Registry . . . . . 7
3.6. Add SMI Security for S/MIME Algorithms Registry . . . . . 9 3.6. Add SMI Security for S/MIME Algorithms Registry . . . . . 9
3.7. Add SMI Security for S/MIME Certificate Distribution 3.7. Add SMI Security for S/MIME Certificate Distribution
Registry . . . . . . . . . . . . . . . . . . . . . . . . . 9 Registry . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.8. Add SMI Security for S/MIME Signature Policy Qualifier 3.8. Add SMI Security for S/MIME Signature Policy Qualifier
Registry . . . . . . . . . . . . . . . . . . . . . . . . . 9 Registry . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.9. Add SMI Security for S/MIME Commitment Type Identifier 3.9. Add SMI Security for S/MIME Commitment Type Identifier
Registry . . . . . . . . . . . . . . . . . . . . . . . . . 10 Registry . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.10. Add SMI Security for S/MIME Test Security Policies 3.10. Add SMI Security for S/MIME Test Security Policies
Registry . . . . . . . . . . . . . . . . . . . . . . . . 10 Registry . . . . . . . . . . . . . . . . . . . . . . . . 10
3.11. Add SMI Security for S/MIME Control Attributes for 3.11. Add SMI Security for S/MIME Control Attributes for
Symmetric Key Distribution Registry . . . . . . . . . . . 10 Symmetric Key Distribution Registry . . . . . . . . . . . 11
3.12. Add SMI Security for S/MIME Signature Type Identifiers 3.12. Add SMI Security for S/MIME Signature Type Identifiers
Registry . . . . . . . . . . . . . . . . . . . . . . . . 11 Registry . . . . . . . . . . . . . . . . . . . . . . . . 11
3.13. Add SMI Security for S/MIME X.400 Encoded Information 3.13. Add SMI Security for S/MIME X.400 Encoded Information
Types Registry . . . . . . . . . . . . . . . . . . . . . 11 Types Registry . . . . . . . . . . . . . . . . . . . . . 11
3.14. Add SMI Security for S/MIME Non-cryptographic 3.14. Add SMI Security for S/MIME Non-cryptographic
Capabilities Registry . . . . . . . . . . . . . . . . . . 12 Capabilities Registry . . . . . . . . . . . . . . . . . . 12
3.15. Add SMI Security for S/MIME Portable Symmetric Key 3.15. Add SMI Security for S/MIME Portable Symmetric Key
Container (PSKC) Attributes Registry . . . . . . . . . . 12 Container (PSKC) Attributes Registry . . . . . . . . . . 12
4. Security Considerations . . . . . . . . . . . . . . . . . . . 13 4. Security Considerations . . . . . . . . . . . . . . . . . . . 13
5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
skipping to change at page 4, line 45 skipping to change at page 4, line 45
--------------------- ----- --------------------- ---------- --------------------- ----- --------------------- ----------
1.2.840.113549.1.9.16 smime S/MIME Mail Security {This RFC} 1.2.840.113549.1.9.16 smime S/MIME Mail Security {This RFC}
3.2. Add SMI Security for S/MIME Mail Security Registry 3.2. Add SMI Security for S/MIME Mail Security Registry
Within the SMI-numbers registry, add a "SMI Security for S/MIME Mail Within the SMI-numbers registry, add a "SMI Security for S/MIME Mail
Security (1.2.840.113549.1.9.16)" table with three columns: Security (1.2.840.113549.1.9.16)" table with three columns:
Decimal Description References Decimal Description References
------- -------------------------------------- ---------- ------- -------------------------------------- ----------
0 module-identifiers {This RFC} 0 Module identifiers {This RFC}
1 cms-content-types {This RFC} 1 CMS content types {This RFC}
2 attributes {This RFC} 2 Attributes {This RFC}
3 algorithm-identifiers {This RFC} 3 Algorithm identifiers {This RFC}
4 certificate-distribution {This RFC} 4 Certificate distribution {This RFC}
5 signature-policy-qualifiers {This RFC} 5 Signature policy qualifiers {This RFC}
6 commitment-type-identifiers {This RFC} 6 Commitment type identifiers {This RFC}
7 test-security-policies {This RFC} 7 Test security policies {This RFC}
8 symmetric-key-dist-ctrl-attrs {This RFC} 8 Symmetric key dist ctrl attrs {This RFC}
9 signature-type-identifier {This RFC} 9 Signature type identifiers {This RFC}
10 encoded-information-types {This RFC} 10 Encoded information types {This RFC}
11 smime-capabilities {This RFC} 11 S/MIME capabilities {This RFC}
12 pskc-attributes {This RFC} 12 PSKC attributes {This RFC}
Future updates to this table require Expert Review as defined in Future updates to this table require Expert Review as defined in
[RFC5226]. [RFC5226].
3.3. Add SMI Security for S/MIME Module Identifier Registry 3.3. Add SMI Security for S/MIME Module Identifier Registry
Within the SMI-numbers registry, add a "SMI Security for S/MIME Within the SMI-numbers registry, add a "SMI Security for S/MIME
Module Identifier (1.2.840.113549.1.9.16.0)" table with three Module Identifier (1.2.840.113549.1.9.16.0)" table with three
columns: columns:
skipping to change at page 14, line 29 skipping to change at page 14, line 30
[RFC3114] Nicolls, W., "Implementing Company Classification Policy [RFC3114] Nicolls, W., "Implementing Company Classification Policy
with the S/MIME Security Label", RFC 3114, May 2002. with the S/MIME Security Label", RFC 3114, May 2002.
[RFC3125] Ross, J., Pinkas, D., and N. Pope, "Electronic Signature [RFC3125] Ross, J., Pinkas, D., and N. Pope, "Electronic Signature
Policies", RFC 3125, September 2001. Policies", RFC 3125, September 2001.
[RFC3126] Pinkas, D., Ross, J., and N. Pope, "Electronic Signature [RFC3126] Pinkas, D., Ross, J., and N. Pope, "Electronic Signature
Formats for long term electronic signatures", RFC 3126, Formats for long term electronic signatures", RFC 3126,
September 2001. September 2001.
[RFC3161] Adams, C., Cain, P., Pinkas, D., and R. Zuccherato,
"Internet X.509 Public Key Infrastructure Time-Stamp
Protocol (TSP)", RFC 3161, August 2001.
[RFC3183] Dean, T. and W. Ottaway, "Domain Security Services using [RFC3183] Dean, T. and W. Ottaway, "Domain Security Services using
S/MIME", RFC 3183, October 2001. S/MIME", RFC 3183, October 2001.
[RFC3185] Farrell, S. and S. Turner, "Reuse of CMS Content [RFC3185] Farrell, S. and S. Turner, "Reuse of CMS Content
Encryption Keys", RFC 3185, October 2001. Encryption Keys", RFC 3185, October 2001.
[RFC3211] Gutmann, P., "Password-based Encryption for CMS", [RFC3211] Gutmann, P., "Password-based Encryption for CMS",
RFC 3211, December 2001. RFC 3211, December 2001.
[RFC3274] Gutmann, P., "Compressed Data Content Type for [RFC3274] Gutmann, P., "Compressed Data Content Type for
skipping to change at page 16, line 17 skipping to change at page 16, line 23
Authenticated-Enveloped-Data Content Type", RFC 5083, Authenticated-Enveloped-Data Content Type", RFC 5083,
November 2007. November 2007.
[RFC5084] Housley, R., "Using AES-CCM and AES-GCM Authenticated [RFC5084] Housley, R., "Using AES-CCM and AES-GCM Authenticated
Encryption in the Cryptographic Message Syntax (CMS)", Encryption in the Cryptographic Message Syntax (CMS)",
RFC 5084, November 2007. RFC 5084, November 2007.
[RFC5126] Pinkas, D., Pope, N., and J. Ross, "CMS Advanced [RFC5126] Pinkas, D., Pope, N., and J. Ross, "CMS Advanced
Electronic Signatures (CAdES)", RFC 5126, March 2008. Electronic Signatures (CAdES)", RFC 5126, March 2008.
[RFC5272] Schaad, J. and M. Myers, "Certificate Management over CMS
(CMC)", RFC 5272, June 2008.
[RFC5275] Turner, S., "CMS Symmetric Key Management and [RFC5275] Turner, S., "CMS Symmetric Key Management and
Distribution", RFC 5275, June 2008. Distribution", RFC 5275, June 2008.
[RFC5485] Housley, R., "Digital Signatures on Internet-Draft [RFC5485] Housley, R., "Digital Signatures on Internet-Draft
Documents", RFC 5485, March 2009. Documents", RFC 5485, March 2009.
[RFC5544] Santoni, A., "Syntax for Binding Documents with Time- [RFC5544] Santoni, A., "Syntax for Binding Documents with Time-
Stamps", RFC 5544, February 2010. Stamps", RFC 5544, February 2010.
[RFC5649] Housley, R. and M. Dworkin, "Advanced Encryption Standard [RFC5649] Housley, R. and M. Dworkin, "Advanced Encryption Standard
skipping to change at page 18, line 4 skipping to change at page 18, line 13
(RPKI)", RFC 6486, February 2012. (RPKI)", RFC 6486, February 2012.
[RFC6493] Bush, R., "The Resource Public Key Infrastructure (RPKI) [RFC6493] Bush, R., "The Resource Public Key Infrastructure (RPKI)
Ghostbusters Record", RFC 6493, February 2012. Ghostbusters Record", RFC 6493, February 2012.
[RFC7030] M. Pritikin, M., P. Yee, and D. Harkins, "Enrollment over [RFC7030] M. Pritikin, M., P. Yee, and D. Harkins, "Enrollment over
Secure Transport", RFC 7030, October 2013. Secure Transport", RFC 7030, October 2013.
[WIP1] Herzog, J., and R. Khazan, "A set-key attribute for [WIP1] Herzog, J., and R. Khazan, "A set-key attribute for
symmetric-key packages", Work in progress, October 2012. symmetric-key packages", Work in progress, October 2012.
[draft-herzog-setkey-07] [draft-herzog-setkey-07]
[WIP2] Housley, R., "Cryptographic Message Syntax (CMS) Key [WIP2] Housley, R., "Cryptographic Message Syntax (CMS) Key
Package Receipt and Error Content Types", Work in Package Receipt and Error Content Types", Work in
progress, October 2013. [draft-housley-ct-keypackage- progress, October 2013. [draft-housley-ct-keypackage-
receipt-n-error-05] receipt-n-error-05]
[WIP3] Housley, R., "Use of the Hash-based Merkle Tree Signature [WIP3] Housley, R., "Use of the Hash-based Merkle Tree Signature
(MTS) Algorithm in the Cryptographic Message Syntax (MTS) Algorithm in the Cryptographic Message Syntax
(CMS)", Work in progress, August 2013. [draft-housley-cms- (CMS)", Work in progress, August 2013. [draft-housley-cms-
mts-hash-sig-00] mts-hash-sig-00]
Acknowledgements Acknowledgements
Thanks to Jim Schaad, Sean Turner, and Carl Wallace for their review Many thanks to Suresh Krishnan, Jim Schaad, Sean Turner, and Carl
and comments. Wallace for their careful review and comments.
Author's Addresses Author's Addresses
Russ Housley Russ Housley
918 Spring Knoll Drive 918 Spring Knoll Drive
Herndon, VA 20170 Herndon, VA 20170
USA USA
EMail: housley@vigilsec.com EMail: housley@vigilsec.com
 End of changes. 9 change blocks. 
20 lines changed or deleted 26 lines changed or added

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