Trusted Execution Environment Provisioning (TEEP) Protocol
draft-ietf-teep-protocol-26

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-teep-protocol@ietf.org, kondtir@gmail.com, paul.wouters@aiven.io, rfc-editor@rfc-editor.org, teep-chairs@ietf.org, teep@ietf.org
Subject: Protocol Action: 'Trusted Execution Environment Provisioning (TEEP) Protocol' to Proposed Standard (draft-ietf-teep-protocol-26.txt)

The IESG has approved the following document:
- 'Trusted Execution Environment Provisioning (TEEP) Protocol'
  (draft-ietf-teep-protocol-26.txt) as Proposed Standard

This document is the product of the Trusted Execution Environment
Provisioning Working Group.

The IESG contact persons are Paul Wouters and Deb Cooley.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-teep-protocol/

Ballot Text

Technical Summary

   This document specifies a protocol that installs, updates, and
   deletes Trusted Components in a device with a Trusted Execution
   Environment (TEE).  This specification defines an interoperable
   protocol for managing the lifecycle of Trusted Components.

Working Group Summary

The draft was adopted in Dec, 2017 with good WG support for adoption. It has
been thoroughly reviewed by working group members. The authors have given
updates on progress of the draft during all of the WG meetings. A number of
detailed reviews of the document were posted to the working group mailing list,
along with the issues and pull requests logged on GitHub. Further, there has
been active participation in IETF Hackathon activities from WG members to
implement, test and interop TEEP protocol.  The authors of this document have
extensive experience with the TEE technologies and implementations.
There was good feedback during IETF LC that resulted in a strongly improved
document. There were no controversies.


Document Quality

Multiple open source code repositories of the TEEP protocol is available and
are listed in the "Additional resources" Section of
https://datatracker.ietf.org/doc/draft-ietf-teep-protocol/. The protocol was
implemented and interop was done during IETF hackathons to identify and fix
issues. IETF hackathon reports were presented in the WG meetings.

The TEEP protocol uses CBOR and relies on COSE for security. It leverages the
work in SUIT (SUIT manifest format is used) and RATS (EAT format is used) WGs.
The draft has been reviewed by members actively contributing to these working
groups. CBOR's CDDL validation was done for every commit (see https://github.com/ietf-teep/teep-protocol)


Personnel

   The Document Shepherd for this document is Tirumaleswar Reddy.K. The
   Responsible Area Director is Paul Wouters.

RFC Editor Note