<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-teep-architecture" target="https://datatracker.ietf.org/doc/html/draft-ietf-teep-architecture-18">
   <front>
      <title>Trusted Execution Environment Provisioning (TEEP) Architecture</title>
      <author initials="M." surname="Pei" fullname="Mingliang Pei">
         <organization>Broadcom</organization>
      </author>
      <author initials="H." surname="Tschofenig" fullname="Hannes Tschofenig">
         <organization>Arm Limited</organization>
      </author>
      <author initials="D." surname="Thaler" fullname="Dave Thaler">
         <organization>Microsoft</organization>
      </author>
      <author initials="D. M." surname="Wheeler" fullname="Dave Wheeler">
         <organization>Amazon</organization>
      </author>
      <date month="July" day="11" year="2022" />
      <abstract>
	 <t>   A Trusted Execution Environment (TEE) is an environment that enforces
   that any code within that environment cannot be tampered with, and
   that any data used by such code cannot be read or tampered with by
   any code outside that environment.  This architecture document
   motivates the design and standardization of a protocol for managing
   the lifecycle of trusted applications running inside such a TEE.

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