The Open Trust Protocol (OTrP)
draft-ietf-teep-opentrustprotocol-03
TEEP M. Pei
Internet-Draft Symantec
Intended status: Informational A. Atyeo
Expires: November 16, 2019 Intercede
N. Cook
ARM Ltd.
M. Yoo
IoTrust
H. Tschofenig
ARM Ltd.
May 15, 2019
The Open Trust Protocol (OTrP)
draft-ietf-teep-opentrustprotocol-03.txt
Abstract
This document specifies the Open Trust Protocol (OTrP), a protocol
that follows the Trust Execution Environment Provisioning (TEEP)
architecture and provides a message protocol that provisions and
manages Trusted Applications into a device with a Trusted Execution
Environment (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 November 16, 2019.
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
Pei, et al. Expires November 16, 2019 [Page 1]
Internet-Draft OTrP May 2019
(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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 6
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Definitions . . . . . . . . . . . . . . . . . . . . . . . 6
3.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 6
4. OTrP Entities and Trust Model . . . . . . . . . . . . . . . . 6
4.1. System Components . . . . . . . . . . . . . . . . . . . . 6
4.2. Trust Anchors in TEE . . . . . . . . . . . . . . . . . . 7
4.3. Trust Anchors in TAM . . . . . . . . . . . . . . . . . . 7
4.4. Keys and Certificate Types . . . . . . . . . . . . . . . 7
5. Protocol Scope and Entity Relations . . . . . . . . . . . . . 10
5.1. A Sample Device Setup Flow . . . . . . . . . . . . . . . 12
5.2. Derived Keys in The Protocol . . . . . . . . . . . . . . 12
5.3. Security Domain Hierarchy and Ownership . . . . . . . . . 13
5.4. SD Owner Identification and TAM Certificate Requirements 13
5.5. Service Provider Container . . . . . . . . . . . . . . . 14
6. OTrP Broker . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.1. Role of OTrP Broker . . . . . . . . . . . . . . . . . . . 15
6.2. OTrP Broker and Global Platform TEE Client API . . . . . 16
6.3. OTrP Broker Implementation Consideration . . . . . . . . 16
6.3.1. OTrP Broker Distribution . . . . . . . . . . . . . . 16
6.3.2. Number of OTrP Broker . . . . . . . . . . . . . . . . 16
6.4. OTrP Broker Interfaces for Client Applications . . . . . 17
6.4.1. ProcessOTrPMessage call . . . . . . . . . . . . . . . 17
6.4.2. GetTAInformation call . . . . . . . . . . . . . . . . 17
6.5. Sample End-to-End Client Application Flow . . . . . . . . 20
6.5.1. Case 1: A New Client Application Uses a TA . . . . . 20
6.5.2. Case 2: A Previously Installed Client Application
Calls a TA . . . . . . . . . . . . . . . . . . . . . 21
7. OTrP Messages . . . . . . . . . . . . . . . . . . . . . . . . 22
Show full document text