Trusted Execution Environment Provisioning (TEEP) Architecture
draft-ietf-teep-architecture-05

The information below is for an old version of the document
Document Type Active Internet-Draft (teep WG)
Last updated 2019-12-12 (latest revision 2019-12-06)
Stream IETF
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document (wg milestones: Mar 2018 - Adopt an Architectur..., Dec 2019 - Begin WGLC for Archi..., Sep 2020 - Progress Architectur... )
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: June 14, 2020                                       Arm Limited
                                                               D. Thaler
                                                               Microsoft
                                                              D. Wheeler
                                                                   Intel
                                                       December 12, 2019

     Trusted Execution Environment Provisioning (TEEP) Architecture
                    draft-ietf-teep-architecture-05

Abstract

   A Trusted Execution Environment (TEE) is an environment that enforces
   that only authorized code can execute with that environment, and that
   any data used by such code cannot be read or tampered with by any
   code outside that environment.  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 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 June 14, 2020.

Copyright Notice

   Copyright (c) 2019 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

Pei, et al.               Expires June 14, 2020                 [Page 1]
Internet-Draft              TEEP Architecture              December 2019

   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.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  Payment . . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.2.  Authentication  . . . . . . . . . . . . . . . . . . . . .   7
     3.3.  Internet of Things  . . . . . . . . . . . . . . . . . . .   7
     3.4.  Confidential Cloud Computing  . . . . . . . . . . . . . .   7
   4.  Architecture  . . . . . . . . . . . . . . . . . . . . . . . .   8
     4.1.  System Components . . . . . . . . . . . . . . . . . . . .   8
     4.2.  Different Renditions of TEEP Architecture . . . . . . . .  10
     4.3.  Multiple TAMs and Relationship to TAs . . . . . . . . . .  12
     4.4.  Untrusted Apps, Trusted Apps, and Personalization Data  .  13
     4.5.  Examples of Application Delivery Mechanisms in Existing
           TEEs  . . . . . . . . . . . . . . . . . . . . . . . . . .  14
     4.6.  Entity Relations  . . . . . . . . . . . . . . . . . . . .  15
   5.  Keys and Certificate Types  . . . . . . . . . . . . . . . . .  17
     5.1.  Trust Anchors in TEE  . . . . . . . . . . . . . . . . . .  18
     5.2.  Trust Anchors in TAM  . . . . . . . . . . . . . . . . . .  19
     5.3.  Scalability . . . . . . . . . . . . . . . . . . . . . . .  19
     5.4.  Message Security  . . . . . . . . . . . . . . . . . . . .  19
   6.  TEEP Broker . . . . . . . . . . . . . . . . . . . . . . . . .  19
Show full document text