#
# Registration template for PKCS#11 URI.
#

According to RFC 4395, Section "5.2. Registration Procedures", and Section "5.4.
URI Scheme Registration Template", this document specifies the registration
template for the PKCS#11 URI registration request.

Template author: Jan Pechanec <jan.pechanec@oracle.com>

The template references sections in the following I-D:

  http://tools.ietf.org/html/draft-pechanec-pkcs11uri-08

#
# Template starts here.
#

URI scheme name: pkcs11 (section "3.1.  PKCS#11 URI Scheme Name")

URI scheme status: permanent (section "3.2.  PKCS#11 URI Scheme Status")

URI scheme syntax: Section "3.3.  PKCS#11 URI Scheme Syntax"

URI scheme semantics: Section "1.  Introduction"

Encoding considerations: Section "3.3.  PKCS#11 URI Scheme Syntax"

Applications/protocols that use this URI scheme name: Section "1.  Introduction"

More specifically, list of applications that already use PKCS#11 URI according
to the existing drafts follows. The list may not be complete.

GnuTLS
	- www.gnutls.org
	- in gnutls_pkcs11_obj_info_t structure
	- parser is in pkcs11_get_info())
Gnome
	- in libgck library used by gnome-keyring since version 3.3.5
	- http://developer.gnome.org/gck/3.6/gck-PKCS11-URIs.html
p11-kit
	- http://cgit.freedesktop.org/p11-glue/p11-kit
	- parsing function is p11_kit_uri_parse()
OpenSC
	- http://www.opensc-project.org
	- uses PKCS#11 URIs via p11-kit
Solaris 11
	- ZFS crypto
		- zfs_encrypt(1M) manual page
	- SunSSH for X.509 based authentication
		- sshd(1M) manual page (section "Using X.509 Certificates as
		  Host Keys and User Identities")

Interoperability considerations: N/A

Security considerations: Section "6.  Security Considerations"

Contact: Jan Pechanec, Darren J. Moffat. Section "Authors' Addresses"

Author/Change Controller: N/A (permanent registration requested, not
provisional)

References: Section "7.  References"