#
# 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-09

#
# 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 we know of that already use
PKCS#11 URI according to the existing drafts follows. The list may not
be complete.

GnuTLS
	- GNU Transport Layer Security Library
	- www.gnutls.org
Gnome
	- used by gnome-keyring since version 3.3.5
	- http://developer.gnome.org/gck/3.6/gck-PKCS11-URIs.html
Solaris 11
	- for referencing keys in ZFS filesystem encryption
	- SunSSH to reference keys/certs used in the X.509 based
	  authentication
p11-kit
	- kit for unification of PKCS#11 modules
	- http://cgit.freedesktop.org/p11-glue/p11-kit
OpenSC
	- tools and libraries for smart cards
	- https://www.opensc-project.org/opensc
	- uses PKCS#11 URIs via p11-kit
OpenConnect
	- client for Cisco's AnyConnect SSL VPN
	- http://www.infradead.org/openconnect/
	- uses PKCS#11 URIs via p11-kit

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"

vim:textwidth=72