Trusted Execution Environment Provisioning (TEEP) Protocol
draft-tschofenig-teep-protocol-00
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (teep WG)
|
|
Last updated |
|
2019-11-05
(latest revision 2019-11-04)
|
|
Replaces |
|
draft-tschofenig-teep-otrp-v2
|
|
Replaced by |
|
draft-ietf-teep-protocol
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized
bibtex
|
| Stream |
WG state
|
|
Candidate for WG Adoption
|
|
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: Standards Track H. Tschofenig
Expires: May 7, 2020 Arm Ltd.
D. Wheeler
Intel
November 4, 2019
Trusted Execution Environment Provisioning (TEEP) Protocol
draft-tschofenig-teep-protocol-00
Abstract
This document specifies a protocol that installs, updates, and
deletes Trusted Applications (TAs) in a device with a Trusted
Execution Environment (TEE). Due to its function it is called
"Trusted Execution Environment Provisioning (TEEP) Protocol", which
provides interoperability for mantaining the lifecycle of TAs.
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 7, 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
(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
Pei, et al. Expires May 7, 2020 [Page 1]
Internet-Draft TEEP Protocol November 2019
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 . . . . . . . . . . . . . . . . . . . . 2
3. Message Overview . . . . . . . . . . . . . . . . . . . . . . 3
4. Detailed Messages Specification . . . . . . . . . . . . . . . 4
5. Security Consideration . . . . . . . . . . . . . . . . . . . 11
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.1. Normative References . . . . . . . . . . . . . . . . . . 15
7.2. Informative References . . . . . . . . . . . . . . . . . 17
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 17
Appendix B. Contributors . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
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.
This document specifies the protocol for communicating between a TAM
and a TEEP Agent, involving a TEEP Broker.
The Trusted Execution Environment Provisioning (TEEP) architecture
document [I-D.ietf-teep-architecture] has set to provide a design
guidance for such an interoperable protocol and introduces the
necessary terminology. Note that the term Trusted Application may
include more than code; it may also include configuration data and
keys needed by the TA to operate correctly.
2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
Pei, et al. Expires May 7, 2020 [Page 2]
Internet-Draft TEEP Protocol November 2019
This specification re-uses the terminology defined in
Show full document text