Cloud of Secure Elements(CoSE)
draft-urien-cfrg-cose-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Pascal Urien | ||
Last updated | 2015-08-11 (Latest revision 2015-02-07) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes an architecture named "Cloud of Secure Elements (CoSE)" whose goal is to strengthen the Internet trust. A Secure element (SE) provides secure services thanks to various means such as tamper resistant technologies or software virtualization techniques. Secure elements are hosted in dedicated servers (i.e. Trusted Secure Elements Servers, TSES); they provide secure storage facilities or compute cryptographic procedures. Secure elements resources are identified by dedicated URIs and should also support HTTP interface. Users are equipped with "Access Credential" and thanks to the Secure Transport Protocol (STP-TSES) remotely access to Secure Element embedded resources. The RACS (Remote APDU Call Secure) and its associated framework protocol is an early proof of concept of the CoSE concept.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)