Internet Engineering Task Force (IETF) R. Housley
Request for Comments: 7299 Vigil Security
Category: Informational July 2014
ISSN: 2070-1721
Object Identifier Registry for the PKIX Working Group
Abstract
When the Public-Key Infrastructure using X.509 (PKIX) Working Group was chartered, an object identifier arc was allocated by IANA for use by that working group. This document describes the object identifiers that were assigned in that arc, returns 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 Section 2 of RFC 5741.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7299.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) 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.
When the Public-Key Infrastructure using X.509 (PKIX) Working Group was chartered, an object identifier arc was allocated by IANA for use by that working group. These object identifiers are primarily used with Abstract Syntax Notation One (ASN.1) [ASN1-88][ASN1-97][ASN1-08]. The ASN.1 specifications continue to evolve, but object identifiers can be used with any and all versions of ASN.1.
This document describes the object identifiers that were assigned in the PKIX arc, returns control of the PKIX arc to IANA, and establishes IANA allocation policies for any future assignments within the PKIX arc.
Twenty-five subordinate object identifier arcs were used, numbered from 0 to 23 and 48. In addition, there are seven subordinate arcs. They were assigned as follows:
The values assigned in each of these subordinate object identifier arcs are discussed in the next section.
Housley Informational [Page 5]
RFC 7299 PKIX OID Registry July 20143. IANA Considerations
IANA has updated one registry table and created 33 additional tables.
Updates to the new tables are to be made according to the Specification Required policy as defined in [RFC5226]. The expert is expected to ensure that any new values are strongly related to the work that was done by the PKIX Working Group. That is, additional object identifiers are to be related to X.509 certificates, X.509 attribute certificates, X.509 certificate revocation lists (CRLs), or protocols associated with them. Object identifiers for other purposes should not be assigned in this arc.
3.1. Update to "SMI Security for Mechanism Codes" Registry
The reference for the Public Key Infrastructure using X.509 (PKIX) entry (decimal value 7) has been updated to point to this document.
Future updates to this table are to be made according to the Specification Required policy as defined in [RFC5226].
3.6. "SMI Security for PKIX Extended Key Purpose" Registry
Within the SMI-numbers registry, an "SMI Security for PKIX Extended Key Purpose Identifiers (1.3.6.1.5.5.7.3)" table with three columns has been added:
Note: id-cmc-statusInfo is also known as id-cmc-cMCStatusInfo.
Future updates to this table are to be made according to the Specification Required policy as defined in [RFC5226].
3.13. "SMI Security for PKIX CMC GLA Requests and Responses" Registry
Within the SMI-numbers registry, an "SMI Security for PKIX CMC GLA Requests and Responses (1.3.6.1.5.5.7.7.99)" table with three columns has been added:
Future updates to this table are to be made according to the Specification Required policy as defined in [RFC5226].
Housley Informational [Page 15]
RFC 7299 PKIX OID Registry July 20143.16. "SMI Security for PKIX Attribute Certificate Attributes" Registry
Within the SMI-numbers registry, an "SMI Security for PKIX Attribute Certificate Attributes (1.3.6.1.5.5.7.10)" table with three columns has been added:
Future updates to this table are to be made according to the Specification Required policy as defined in [RFC5226].
3.17. "SMI Security for PKIX Qualified Certificate Statements" Registry
Within the SMI-numbers registry, an "SMI Security for PKIX Qualified Certificate Statements (1.3.6.1.5.5.7.11)" table with three columns has been added:
Future updates to this table are to be made according to the Specification Required policy as defined in [RFC5226]. 3.25. "SMI Security for PKIX SCVP Validation Policies and Algorithms" Registry
Within the SMI-numbers registry, an "SMI Security for PKIX SCVP Validation Policies and Algorithms (1.3.6.1.5.5.7.19)" table with three columns has been added:
Note: id-svp-basicValAlg is also known as id-bvae.
Note: id-svp-dnValAlg is also known as id-dnvae and id-nva-dnCompAlg.
Future updates to this table are to be made according to the Specification Required policy as defined in [RFC5226].
3.26. "SMI Security for PKIX SCVP Name Validation Policy Errors" Registry
Within the SMI-numbers registry, an "SMI Security for PKIX SCVP Name Validation Policy Errors (1.3.6.1.5.5.7.19.2)" table with three columns has been added:
Future updates to this table are to be made according to the Specification Required policy as defined in [RFC5226]. 3.27. "SMI Security for PKIX SCVP Basic Validation Policy Errors" Registry
Within the SMI-numbers registry, an "SMI Security for PKIX SCVP Basic Validation Policy Errors (1.3.6.1.5.5.7.19.3)" table with three columns has been added:
Future updates to this table are to be made according to the Specification Required policy as defined in [RFC5226].
3.28. "SMI Security for PKIX SCVP Distinguished Name Validation Policy Errors" Registry
Within the SMI-numbers registry, an "SMI Security for PKIX SCVP Distinguished Name Validation Policy Errors (1.3.6.1.5.5.7.19.4)" table with three columns has been added:
Future updates to this table are to be made according to the Specification Required policy as defined in [RFC5226].
3.30. "SMI Security for PKIX Proxy Certificate Policy Languages" Registry
Within the SMI-numbers registry, an "SMI Security for PKIX Proxy Certificate Policy Languages (1.3.6.1.5.5.7.21)" table with three columns has been added:
Future updates to this table are to be made according to the Specification Required policy as defined in [RFC5226].
Housley Informational [Page 22]
RFC 7299 PKIX OID Registry July 20143.32. "SMI Security for PKIX Subject Key Identifier Semantics" Registry
Within the SMI-numbers registry, an "SMI Security for PKIX Subject Key Identifier Semantics (1.3.6.1.5.5.7.23)" table with three columns has been added:
Future updates to this table are to be made according to the Specification Required policy as defined in [RFC5226]. 3.34. "SMI Security for PKIX Online Certificate Status Protocol (OCSP)" Registry
Within the SMI-numbers registry, an "SMI Security for PKIX Online Certificate Status Protocol (OCSP) (1.3.6.1.5.5.7.48.1)" table with three columns has been added:
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.
The id-pe-nsa certificate extension should not appear in any certificate that is used on the public Internet.
Housley Informational [Page 24]
RFC 7299 PKIX OID Registry July 20145. References5.1. Normative References
[ASN1-08] International Telecommunication Union, "Abstract Syntax
Notation One (ASN.1): Specification of basic notation", ITU-T Recommendation X.680, November 2008.
[ASN1-88] International Telephone and Telegraph Consultative
Committee, "Specification of Abstract Syntax Notation One (ASN.1)", CCITT Recommendation X.208, 1988.
[ASN1-97] International Telecommunication Union, "Abstract Syntax
Notation One (ASN.1): Specification of basic notation", ITU-T Recommendation X.680, 1997.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[Abley] Abley, J., Schlyter, J., and G. Bailey, "DNSSEC Trust
Anchor Publication for the Root Zone", Work in Progress, June 2014.
[BGPSEC] Reynolds, M., Turner, S., and S. Kent, "A Profile for
BGPSEC Router Certificates, Certificate Revocation Lists, and Certification Requests", Work in Progress, March 2014.
[RFC2459] Housley, R., Ford, W., Polk, W., and D. Solo, "Internet
X.509 Public Key Infrastructure Certificate and CRL Profile", RFC 2459, January 1999.
[RFC2510] Adams, C. and S. Farrell, "Internet X.509 Public Key
Infrastructure Certificate Management Protocols", RFC 2510, March 1999.
[RFC2511] Myers, M., Adams, C., Solo, D., and D. Kemp, "Internet
X.509 Certificate Request Message Format", RFC 2511, March 1999.
[RFC2528] Housley, R. and W. Polk, "Internet X.509 Public Key
Infrastructure Representation of Key Exchange Algorithm (KEA) Keys in Internet X.509 Public Key Infrastructure Certificates", RFC 2528, March 1999.
[RFC2560] Myers, M., Ankney, R., Malpani, A., Galperin, S., and C.
Adams, "X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP", RFC 2560, June 1999.
[RFC2797] Myers, M., Liu, X., Schaad, J., and J. Weinstein,
"Certificate Management Messages over CMS", RFC 2797, April 2000.
[RFC2875] Prafullchandra, H. and J. Schaad, "Diffie-Hellman
Proof-of-Possession Algorithms", RFC 2875, July 2000.
[RFC3029] Adams, C., Sylvester, P., Zolotarev, M., and R.
Zuccherato, "Internet X.509 Public Key Infrastructure Data Validation and Certification Server Protocols", RFC 3029, February 2001.
[RFC3039] Santesson, S., Polk, W., Barzin, P., and M. Nystrom,
"Internet X.509 Public Key Infrastructure Qualified Certificates Profile", RFC 3039, January 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.
[RFC3279] Bassham, L., Polk, W., and R. Housley, "Algorithms and
Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile", RFC 3279, April 2002.
[RFC3280] Housley, R., Polk, W., Ford, W., and D. Solo, "Internet
X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile", RFC 3280, April 2002.
[RFC3281] Farrell, S. and R. Housley, "An Internet Attribute
Certificate Profile for Authorization", RFC 3281, April 2002.
[RFC3709] Santesson, S., Housley, R., and T. Freeman, "Internet
X.509 Public Key Infrastructure: Logotypes in X.509 Certificates", RFC 3709, February 2004.
[RFC3739] Santesson, S., Nystrom, M., and T. Polk, "Internet X.509
Public Key Infrastructure: Qualified Certificates Profile", RFC 3739, March 2004.
[RFC3770] Housley, R. and T. Moore, "Certificate Extensions and
Attributes Supporting Authentication in Point-to-Point Protocol (PPP) and Wireless Local Area Networks (WLAN)", RFC 3770, May 2004.
[RFC3779] Lynn, C., Kent, S., and K. Seo, "X.509 Extensions for IP
Addresses and AS Identifiers", RFC 3779, June 2004.
[RFC3820] Tuecke, S., Welch, V., Engert, D., Pearlman, L., and M.
Thompson, "Internet X.509 Public Key Infrastructure (PKI) Proxy Certificate Profile", RFC 3820, June 2004.
[RFC3920] Saint-Andre, P., Ed., "Extensible Messaging and Presence
Protocol (XMPP): Core", RFC 3920, October 2004.
[RFC4043] Pinkas, D. and T. Gindin, "Internet X.509 Public Key
Infrastructure Permanent Identifier", RFC 4043, May 2005.
[RFC4055] Schaad, J., Kaliski, B., and R. Housley, "Additional
Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile", RFC 4055, June 2005.
[RFC4059] Linsenbardt, D., Pontius, S., and A. Sturgeon, "Internet
X.509 Public Key Infrastructure Warranty Certificate Extension", RFC 4059, May 2005.
[RFC4108] Housley, R., "Using Cryptographic Message Syntax (CMS) to
Protect Firmware Packages", RFC 4108, August 2005.
[RFC4210] Adams, C., Farrell, S., Kause, T., and T. Mononen,
"Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP)", RFC 4210, September 2005.
[RFC4334] Housley, R. and T. Moore, "Certificate Extensions and
Attributes Supporting Authentication in Point-to-Point Protocol (PPP) and Wireless Local Area Networks (WLAN)", RFC 4334, February 2006.
[RFC4387] Gutmann, P., Ed., "Internet X.509 Public Key
Infrastructure Operational Protocols: Certificate Store Access via HTTP", RFC 4387, February 2006.
[RFC4476] Francis, C. and D. Pinkas, "Attribute Certificate (AC)
Policies Extension", RFC 4476, May 2006.
[RFC4683] Park, J., Lee, J., . Lee, H., Park, S., and T. Polk,
"Internet X.509 Public Key Infrastructure Subject Identification Method (SIM)", RFC 4683, October 2006.
[RFC4945] Korver, B., "The Internet IP Security PKI Profile of
IKEv1/ISAKMP, IKEv2, and PKIX", RFC 4945, August 2007.
[RFC4985] Santesson, S., "Internet X.509 Public Key Infrastructure
Subject Alternative Name for Expression of Service Name", RFC 4985, August 2007.
[RFC5055] Freeman, T., Housley, R., Malpani, A., Cooper, D., and W.
Polk, "Server-Based Certificate Validation Protocol (SCVP)", RFC 5055, December 2007.
[RFC5272] Schaad, J. and M. Myers, "Certificate Management over CMS
(CMC)", RFC 5272, June 2008.
[RFC5275] Turner, S., "CMS Symmetric Key Management and
Distribution", RFC 5275, June 2008.
[RFC5276] Wallace, C., "Using the Server-Based Certificate
Validation Protocol (SCVP) to Convey Long-Term Evidence Records", RFC 5276, August 2008.
[RFC5415] Calhoun, P., Ed., Montemurro, M., Ed., and D. Stanley,
Ed., "Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification", RFC 5415, March 2009.
[RFC5480] Turner, S., Brown, D., Yiu, K., Housley, R., and T. Polk,
"Elliptic Curve Cryptography Subject Public Key Information", RFC 5480, March 2009.
[RFC5697] Farrell, S., "Other Certificates Extension", RFC 5697,
November 2009.
[RFC5755] Farrell, S., Housley, R., and S. Turner, "An Internet
Attribute Certificate Profile for Authorization", RFC 5755, January 2010.
[RFC5912] Hoffman, P. and J. Schaad, "New ASN.1 Modules for the
Public Key Infrastructure Using X.509 (PKIX)", RFC 5912, June 2010.
[RFC5913] Turner, S. and S. Chokhani, "Clearance Attribute and
Authority Clearance Constraints Certificate Extension", RFC 5913, June 2010.
[RFC5915] Turner, S. and D. Brown, "Elliptic Curve Private Key
Structure", RFC 5915, June 2010.
[RFC5924] Lawrence, S. and V. Gurbani, "Extended Key Usage (EKU) for
Session Initiation Protocol (SIP) X.509 Certificates", RFC 5924, June 2010.
[RFC5934] Housley, R., Ashmore, S., and C. Wallace, "Trust Anchor
Management Protocol (TAMP)", RFC 5934, August 2010.
[RFC5940] Turner, S. and R. Housley, "Additional Cryptographic
Message Syntax (CMS) Revocation Information Choices", RFC 5940, August 2010.
[RFC6010] Housley, R., Ashmore, S., and C. Wallace, "Cryptographic
Message Syntax (CMS) Content Constraints Extension", RFC 6010, September 2010.
[RFC6170] Santesson, S., Housley, R., Bajaj, S., and L. Rosenthol,
"Internet X.509 Public Key Infrastructure -- Certificate Image", RFC 6170, May 2011.
[RFC6187] Igoe, K. and D. Stebila, "X.509v3 Certificates for Secure
Shell Authentication", RFC 6187, March 2011.
[RFC6268] 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)", RFC 6268, July 2011.
[RFC6277] Santesson, S. and P. Hallam-Baker, "Online Certificate
Status Protocol Algorithm Agility", RFC 6277, June 2011.
[RFC6402] Schaad, J., "Certificate Management over CMS (CMC)
Updates", RFC 6402, November 2011.
[RFC6484] Kent, S., Kong, D., Seo, K., and R. Watro, "Certificate
Policy (CP) for the Resource Public Key Infrastructure (RPKI)", BCP 173, RFC 6484, February 2012.
[RFC6487] Huston, G., Michaelson, G., and R. Loomans, "A Profile for
X.509 PKIX Resource Certificates", RFC 6487, February 2012.
[RFC6494] Gagliano, R., Krishnan, S., and A. Kukec, "Certificate
Profile and Certificate Management for SEcure Neighbor Discovery (SEND)", RFC 6494, February 2012.
[RFC6664] Schaad, J., "S/MIME Capabilities for Public Key
Definitions", RFC 6664, July 2012.
[RFC6955] Schaad, J. and H. Prafullchandra, "Diffie-Hellman
Proof-of-Possession Algorithms", RFC 6955, May 2013.
[RFC6960] Santesson, S., Myers, M., Ankney, R., Malpani, A.,
Galperin, S., and C. Adams, "X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP", RFC 6960, June 2013.
[RFC7169] Turner, S., "The NSA (No Secrecy Afforded) Certificate
Extension", RFC 7169, April 1 2014.
[RFC7229] Housley, R., "Object Identifiers for Test Certificate
Policies", RFC 7229, May 2014.
Acknowledgements
Many thanks to Lynne Bartholomew, David Cooper, Jim Schaad, and Sean Turner for their careful review and comments.
Author's Address
Russ Housley 918 Spring Knoll Drive Herndon, VA 20170 USA
EMail: housley@vigilsec.com
Housley Informational [Page 30]
Ad
Translate documents to 日本語, svenska, Nederlands, Deutsch, français, русский, italiano, español, Tiếng Việt, polski, português, 中文, українська, català, norsk, فارسی, suomi, Bahasa Indonesia, العربية, čeština, 한국어, Bahasa Melayu, magyar, română, српски and other languages.