<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-teep-protocol" target="https://datatracker.ietf.org/doc/html/draft-ietf-teep-protocol-26">
   <front>
      <title>Trusted Execution Environment Provisioning (TEEP) Protocol</title>
      <author initials="H." surname="Tschofenig" fullname="Hannes Tschofenig">
         <organization>University of Applied Sciences Bonn-Rhein-Sieg</organization>
      </author>
      <author initials="M." surname="Pei" fullname="Mingliang Pei">
         <organization>Broadcom</organization>
      </author>
      <author initials="D. M." surname="Wheeler" fullname="Dave Wheeler">
         <organization>Amazon</organization>
      </author>
      <author initials="D." surname="Thaler" fullname="Dave Thaler">
         <organization>Microsoft</organization>
      </author>
      <author initials="A." surname="Tsukamoto" fullname="Akira Tsukamoto">
         <organization>Openchip &amp; Software Technologies, S.L.</organization>
      </author>
      <date month="February" day="26" year="2026" />
      <abstract>
	 <t>   This document specifies the Trusted Execution Environment
   Provisioning (TEEP) Protocol, which enables secure lifecycle
   management of Trusted Components in devices with a Trusted Execution
   Environment (TEE).  The protocol defines message exchanges between a
   Trusted Application Manager (TAM) and a TEEP Agent to query device
   state, convey attestation evidence, and install, update, or delete
   Trusted Components.  Messages are encoded in CBOR and secured using
   COSE.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-teep-protocol-26" />
   
</reference>
