A Protocol for Dynamic Trusted Execution Environment Enablement
draft-liu-opentrustprotocol-usecase-01
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-07-03
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group D. Liu
Internet-Draft Q. Fang
Intended status: Informational Alibaba Group
Expires: January 4, 2018 July 3, 2017
A Protocol for Dynamic Trusted Execution Environment Enablement
draft-liu-opentrustprotocol-usecase-01
Abstract
This document describes features of a open trust protocol and related
use cases. With the Open Trust Protocol, see
https://tools.ietf.org/html/draft-pei-opentrustprotocol-03, we have
been trying to develop this application layer security protocol that
allows the management of credentials and the update of such
applications.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 4, 2018.
Copyright Notice
Copyright (c) 2017 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
Liu & Fang Expires January 4, 2018 [Page 1]
Internet-Draft opentrustprotocol July 2017
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Scenario and usecase of OtrP . . . . . . . . . . . . . . . . 4
4.1. Use Case 1 - Payment . . . . . . . . . . . . . . . . . . 7
4.2. Use Case 2 - IoT . . . . . . . . . . . . . . . . . . . . 8
5. The functional requirements generated by the scenario and
usecase . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.1. Use Case 1 - Resource-constrained interaction and
multicast . . . . . . . . . . . . . . . . . . . . . . . . 9
5.2. Use Case 2 - TA and SD management owned by OEM and SP . . 9
5.3. Use Case 3 - Batch mode . . . . . . . . . . . . . . . . . 10
5.4. Use Case 4 - personalization data management . . . . . . 10
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
7. Security Considerations . . . . . . . . . . . . . . . . . . . 11
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
8.1. Normative References . . . . . . . . . . . . . . . . . . 11
8.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Acronyms
CA Certificate Authority
OTrP Open Trust Protocol
REE Rich Execution Environment
SD Security Domain
SP Service Provider
SBM Secure Boot Module
TA Trusted Application
TEE Trusted Execution Environment
TFW Trusted Firmware
TSM Trusted Service Manager
Liu & Fang Expires January 4, 2018 [Page 2]
Internet-Draft opentrustprotocol July 2017
2. Introduction
Chips used on smart phones, tablets, and many consumer appliances
today have built-in support for a so-called Trusted Execution
Environment (TEE). The TEE is a security concept that separates
normal operating systems, like Linux, from code that requires higher
security protection, like security-related code. The underlying idea
of this sandboxing approach is to have smaller code that is better
reviewed and test and to provide it with more rights. They run on
Show full document text