Trusted Execution Environment Provisioning Protocol (teep-p)
draft-tschofenig-teep-protocol-01
TEEP H. Tschofenig
Internet-Draft Arm Ltd.
Intended status: Standards Track M. Pei
Expires: May 20, 2020 Broadcom
D. Wheeler
Intel
D. Thaler
Microsoft
November 17, 2019
Trusted Execution Environment Provisioning Protocol (teep-p)
draft-tschofenig-teep-protocol-01
Abstract
This document specifies a protocol that installs, updates, and
deletes Trusted Applications (TAs) in a device with a Trusted
Execution Environment (TEE). This specification defines an
interoperable protocol for managing the lifecycle of TAs.
The protocol name is teep-p, pronounced teepee. This conjures an
image of a wedge-shaped protective covering for one's belongings,
which sort of matches the intent of this protocol.
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 May 20, 2020.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
Tschofenig, et al. Expires May 20, 2020 [Page 1]
Internet-Draft TEEP Protocol November 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. Message Overview . . . . . . . . . . . . . . . . . . . . . . 3
4. Detailed Messages Specification . . . . . . . . . . . . . . . 5
4.1. QueryRequest . . . . . . . . . . . . . . . . . . . . . . 5
4.2. QueryResponse . . . . . . . . . . . . . . . . . . . . . . 7
4.3. TrustedAppInstall . . . . . . . . . . . . . . . . . . . . 9
4.4. TrustedAppDelete . . . . . . . . . . . . . . . . . . . . 9
4.5. Success . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.6. Error . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5. Ciphersuites . . . . . . . . . . . . . . . . . . . . . . . . 12
6. Security Consideration . . . . . . . . . . . . . . . . . . . 13
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
7.1. Media Type Registration . . . . . . . . . . . . . . . . . 14
7.2. Error Code Registry . . . . . . . . . . . . . . . . . . . 16
7.3. Ciphersuite Registry . . . . . . . . . . . . . . . . . . 17
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.1. Normative References . . . . . . . . . . . . . . . . . . 17
8.2. Informative References . . . . . . . . . . . . . . . . . 18
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 19
Appendix B. Contributors . . . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction
The Trusted Execution Environment (TEE) concept has been designed to
separate a regular operating system, also referred as a Rich
Execution Environment (REE), from security-sensitive applications.
In an TEE ecosystem, different device vendors may use different
operating systems in the REE and may use different types of TEEs.
When application providers or device administrators use Trusted
Application Managers (TAMs) to install, update, and delete Trusted
Applications (TAs) on a wide range of devices with potentially
different TEEs then an interoperability need arises.
Show full document text