Trusted Execution Environment Provisioning (TEEP) Architecture
draft-ietf-teep-architecture-02
|
| Document |
Type |
|
Active Internet-Draft (teep WG)
|
|
Last updated |
|
2019-03-11
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
TEEP M. Pei
Internet-Draft Symantec
Intended status: Informational H. Tschofenig
Expires: September 12, 2019 Arm Limited
D. Wheeler
Intel
A. Atyeo
Intercede
L. Dapeng
Alibaba Group
March 11, 2019
Trusted Execution Environment Provisioning (TEEP) Architecture
draft-ietf-teep-architecture-02
Abstract
A Trusted Execution Environment (TEE) is designed to provide a
hardware-isolation mechanism to separate a regular operating system
from security-sensitive application components.
This architecture document motivates the design and standardization
of a protocol for managing the lifecycle of trusted applications
running inside a TEE.
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 https://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 12, 2019.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
Pei, et al. Expires September 12, 2019 [Page 1]
Internet-Draft TEEP Architecture March 2019
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://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
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . 8
4. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.1. Payment . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.2. Authentication . . . . . . . . . . . . . . . . . . . . . 9
4.3. Internet of Things . . . . . . . . . . . . . . . . . . . 9
4.4. Confidential Cloud Computing . . . . . . . . . . . . . . 9
5. Architecture . . . . . . . . . . . . . . . . . . . . . . . . 9
5.1. System Components . . . . . . . . . . . . . . . . . . . . 9
5.2. Different Renditions of TEEP Architecture . . . . . . . . 12
5.3. Multiple TAMs and Relationship to TAs . . . . . . . . . . 13
5.4. Client Apps, Trusted Apps, and Personalization Data . . . 15
5.5. Examples of Application Delivery Mechanisms in Existing
TEEs . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.6. TEEP Architectural Support for Client App, TA, and
Personalization Data Delivery . . . . . . . . . . . . . . 17
5.7. Entity Relations . . . . . . . . . . . . . . . . . . . . 17
5.8. Trust Anchors in TEE . . . . . . . . . . . . . . . . . . 20
5.9. Trust Anchors in TAM . . . . . . . . . . . . . . . . . . 20
Show full document text