The Open Trust Protocol (OTrP) v2
draft-tschofenig-teep-otrp-v2-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-08
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
TEEP                                                              M. Pei
Internet-Draft                                                  Symantec
Intended status: Standards Track                           H. Tschofenig
Expires: January 9, 2020                                        Arm Ltd.
                                                              D. Wheeler
                                                                   Intel
                                                            July 8, 2019

                   The Open Trust Protocol (OTrP) v2
                    draft-tschofenig-teep-otrp-v2-00

Abstract

   This document specifies the Open Trust Protocol (OTrP) version 2, a
   protocol that provisions and installs, updates, and deletes Trusted
   Applications in 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 January 9, 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
   include Simplified BSD License text as described in Section 4.e of

Pei, et al.              Expires January 9, 2020                [Page 1]
Internet-Draft                    OTrP                         July 2019

   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.  OTrP 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  . . . . . . . . . . . . . . . . .  16
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .  17
   Appendix B.  Contributors . . . . . . . . . . . . . . . . . . . .  17
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

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 version 2 of the Open Trust Protocol (OTrP),
   a protocol for communicating between an OTrP server (as part of a
   TAM) and an OTrP client (which is a client-side component running in
   the REE).

   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.

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].

   This specification re-uses the terminology defined in
   [I-D.ietf-teep-architecture].

Pei, et al.              Expires January 9, 2020                [Page 2]
Internet-Draft                    OTrP                         July 2019

3.  OTrP Message Overview

   OTrP consists of a couple of messages exchanged between a TAM and an
   OTrP Agent via an OTrP Broker.  The messages are encoded either in
   JSON or CBOR and designed to provide end-to-end security.  OTrP
Show full document text