The PKCS #11 URI Scheme
RFC 7512
Document | Type |
RFC - Proposed Standard
(April 2015; Errata)
Was draft-pechanec-pkcs11uri (individual)
|
|
---|---|---|---|
Authors | Jan Pechanec , Darren Moffat | ||
Last updated | 2016-09-29 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | Shawn Emery | ||
Shepherd write-up | Show (last changed 2014-11-05) | ||
IESG | IESG state | RFC 7512 (Proposed Standard) | |
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Stephen Farrell | ||
Send notices to | (None) | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) J. Pechanec Request for Comments: 7512 D. Moffat Category: Standards Track Oracle Corporation ISSN: 2070-1721 April 2015 The PKCS #11 URI Scheme Abstract This memo specifies a PKCS #11 Uniform Resource Identifier (URI) Scheme for identifying PKCS #11 objects stored in PKCS #11 tokens and also for identifying PKCS #11 tokens, slots, or libraries. The URI scheme is based on how PKCS #11 objects, tokens, slots, and libraries are identified in "PKCS #11 v2.20: Cryptographic Token Interface Standard". Status of This Memo This is an Internet Standards Track document. 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). Further information on Internet Standards is available in 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/rfc7512. Copyright Notice Copyright (c) 2015 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. Pechanec & Moffat Standards Track [Page 1] RFC 7512 The PKCS #11 URI Scheme April 2015 Table of Contents 1. Introduction ....................................................2 2. PKCS #11 URI Scheme Definition ..................................4 2.1. PKCS #11 URI Scheme Name ...................................4 2.2. PKCS #11 URI Scheme Status .................................4 2.3. PKCS #11 URI Scheme Syntax .................................4 2.4. PKCS #11 URI Scheme Query Attribute Semantics ..............9 2.5. PKCS #11 URI Matching Guidelines ..........................11 2.6. PKCS #11 URI Comparison ...................................12 2.7. Generating PKCS #11 URIs ..................................14 3. Examples of PKCS #11 URIs ......................................14 4. IANA Considerations ............................................17 4.1. URI Scheme Registration ...................................17 5. Internationalization Considerations ............................18 6. Security Considerations ........................................18 7. References .....................................................19 7.1. Normative References ......................................19 7.2. Informative References ....................................19 Contributors ......................................................20 Authors' Addresses ................................................20 1. Introduction "PKCS #11 v2.20: Cryptographic Token Interface Standard" [PKCS11] specifies an API, called Cryptoki, for devices that hold cryptographic information and perform cryptographic functions. Cryptoki (pronounced "crypto-key" and short for "cryptographic token interface") follows a simple object-based approach, addressing the goals of technology independence (any kind of device may be used) and resource sharing (multiple applications may access multiple devices), presenting applications with a common, logical view of the device -- a cryptographic token. It is desirable for applications or libraries that work with PKCS #11 tokens to accept a common identifier that consumers could use to identify an existing PKCS #11 storage object in a PKCS #11 token, an existing token itself, a slot, or an existing Cryptoki library (also called a producer, module, or provider). The set of storage object types that can be stored in a PKCS #11 token includes a certificate; a data object; and a public, private, or secret key. These objects can be uniquely identifiable via the PKCS #11 URI scheme defined in this document. The set of attributes describing a storage object can contain an object label, its type, and its ID. The set of attributes that identifies a PKCS #11 token can contain a token label, manufacturer name, serial number, and token model. Attributes thatShow full document text