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

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00

TEEP                                                              M. Pei
Internet-Draft                                                  Symantec
Intended status: Informational                             H. Tschofenig
Expires: January 3, 2019                                        Arm Ltd.
                                                                A. Atyeo
                                                               Intercede
                                                                  D. Liu
                                                           Alibaba Group
                                                            July 2, 2018

     Trusted Execution Environment Provisioning (TEEP) Architecture
                  draft-ietf-teep-architecture-00.txt

Abstract

   A Trusted Execution Environment (TEE) was designed to provide a
   hardware-isolation mechanism to separate a regular operating system
   from security- sensitive applications.

   This architecture document motivates the design and standardization
   of a protocol for managing the lifecyle 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 January 3, 2019.

Copyright Notice

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

Pei, et al.              Expires January 3, 2019                [Page 1]
Internet-Draft              TEEP Architecture                  July 2018

   (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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Scope and Assumptions . . . . . . . . . . . . . . . . . . . .   6
   4.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Payment . . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  Authentication  . . . . . . . . . . . . . . . . . . . . .   7
     4.3.  Internet of Things  . . . . . . . . . . . . . . . . . . .   7
     4.4.  Confidential Cloud Computing  . . . . . . . . . . . . . .   7
   5.  Architecture  . . . . . . . . . . . . . . . . . . . . . . . .   7
     5.1.  System Components . . . . . . . . . . . . . . . . . . . .   7
     5.2.  Entity Relations  . . . . . . . . . . . . . . . . . . . .   9
     5.3.  Trust Anchors in TEE  . . . . . . . . . . . . . . . . . .  12
     5.4.  Trust Anchors in TAM  . . . . . . . . . . . . . . . . . .  12
     5.5.  Keys and Certificate Types  . . . . . . . . . . . . . . .  12
     5.6.  Scalability . . . . . . . . . . . . . . . . . . . . . . .  15
     5.7.  Message Security  . . . . . . . . . . . . . . . . . . . .  15
     5.8.  Security Domain Hierarchy and Ownership . . . . . . . . .  15
     5.9.  SD Owner Identification and TAM Certificate Requirements   16
     5.10. Service Provider Container  . . . . . . . . . . . . . . .  17
     5.11. A Sample Device Setup Flow  . . . . . . . . . . . . . . .  17
   6.  Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . .  18
     6.1.  Role of the Agent . . . . . . . . . . . . . . . . . . . .  18
     6.2.  Agent Implementation Consideration  . . . . . . . . . . .  19
       6.2.1.  Agent Distribution  . . . . . . . . . . . . . . . . .  19
       6.2.2.  Number of Agents  . . . . . . . . . . . . . . . . . .  19
   7.  Attestation . . . . . . . . . . . . . . . . . . . . . . . . .  20
     7.1.  Attestation Hierarchy . . . . . . . . . . . . . . . . . .  20
       7.1.1.  Attestation Hierarchy Establishment: Manufacture  . .  20
       7.1.2.  Attestation Hierarchy Establishment: Device Boot  . .  20
       7.1.3.  Attestation Hierarchy Establishment: TAM  . . . . . .  21
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  21
   9.  Security Consideration  . . . . . . . . . . . . . . . . . . .  21