The Open Trust Protocol (OTrP)
draft-ietf-teep-opentrustprotocol-00
Internet Engineering Task Force M. Pei
Internet-Draft Symantec
Intended status: Informational A. Atyeo
Expires: November 2, 2018 Intercede
N. Cook
ARM Ltd.
M. Yoo
Solacia
H. Tschofenig
ARM Ltd.
May 1, 2018
The Open Trust Protocol (OTrP)
draft-ietf-teep-opentrustprotocol-00.txt
Abstract
This document specifies the Open Trust Protocol (OTrP), a protocol to
install, update, and delete applications in a Trusted Execution
Environment (TEE) and to manage their security configuration.
TEEs are used in environments where security services should be
isolated from a regular operating system (often called rich OS).
This form of compartmentalization grants a smaller codebase access to
security sensitive services and restricts communication from the rich
OS to those security services via mediated access.
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 November 2, 2018.
Pei, et al. Expires November 2, 2018 [Page 1]
Internet-Draft OTrP May 2018
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
(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 . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 6
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Definitions . . . . . . . . . . . . . . . . . . . . . . . 6
3.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 8
4. OTrP Entities and Trust Model . . . . . . . . . . . . . . . . 8
4.1. System Components . . . . . . . . . . . . . . . . . . . . 8
4.2. Trusted Anchors in TEE . . . . . . . . . . . . . . . . . 9
4.3. Trusted Anchors in TAM . . . . . . . . . . . . . . . . . 10
4.4. Keys and Certificate Types . . . . . . . . . . . . . . . 10
5. Protocol Scope and Entity Relations . . . . . . . . . . . . . 12
5.1. A Sample Device Setup Flow . . . . . . . . . . . . . . . 14
5.2. Derived Keys in The Protocol . . . . . . . . . . . . . . 15
5.3. Security Domain Hierarchy and Ownership . . . . . . . . . 15
5.4. SD Owner Identification and TAM Certificate Requirements 16
5.5. Service Provider Container . . . . . . . . . . . . . . . 16
6. OTrP Agent . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.1. Role of OTrP Agent . . . . . . . . . . . . . . . . . . . 18
6.2. OTrP Agent and Global Platform TEE Client API . . . . . . 18
6.3. OTrP Agent Implementation Consideration . . . . . . . . . 18
6.3.1. OTrP Agent Distribution . . . . . . . . . . . . . . . 18
6.3.2. Number of OTrP Agent . . . . . . . . . . . . . . . . 19
6.4. OTrP Agent Interfaces for Client Applications . . . . . . 19
6.4.1. ProcessOTrPMessage call . . . . . . . . . . . . . . . 19
6.4.2. GetTAInformation call . . . . . . . . . . . . . . . . 20
6.5. Sample End-to-End Client Application Flow . . . . . . . . 23
6.5.1. Case 1: A New Client Application Uses a TA . . . . . 23
Show full document text