USe Cases and Problem Statement of Open Trust Protocol
draft-liu-opentrustprotocol-usecase-00
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-03-12
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
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 Alibaba Group
Intended status: Informational M. Pei
Expires: September 14, 2017 Symantec
H. Tschofenig
ARM Ltd.
Q. Fang
Alibaba Group
March 13, 2017
USe Cases and Problem Statement of Open Trust Protocol
draft-liu-opentrustprotocol-usecase-00.txt
Abstract
This document discusses use cases of a open trust protocol.
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 September 14, 2017.
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, et al. Expires September 14, 2017 [Page 1]
Internet-Draft opentrustprotocol March 2017
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Scenario and Use Cases of OtrP . . . . . . . . . . . . . . . 4
3.1. Use Case 1 - Payment . . . . . . . . . . . . . . . . . . 6
3.2. Use Case 2 - IoT . . . . . . . . . . . . . . . . . . . . 7
4. Use Case and Functional Requirements related to deployment
scenario . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.1. Use Case 1 - Resource-constrained scenario . . . . . . . 8
4.2. Use Case 2 - TA and SD management owned by OEM and SP . . 8
4.3. Use Case 3 - Batch mode . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1. Normative References . . . . . . . . . . . . . . . . . . 9
7.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. 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
the so-called Secure World (in comparison to the Linux operating
system that would run in the Normal World).
TEEs have been on the market for a while and have been successfully
used for a number of applications, such as payment etc. However, the
technology hasn't reached its full potential since ordinary
developers who could make use of such functionality have a hard time
getting access to it, and to write applications for it.
The industry has been working on an application layer security
protocol that allows to configure security credentials and software
running on a Trusted Execution Environment (TEE) for sometime.
Today, TEEs are, for example, found home routers, set-top boxes,
Show full document text