[Teep] RFC 9397 on Trusted Execution Environment Provisioning (TEEP) Architecture
rfc-editor@rfc-editor.org Fri, 21 July 2023 22:55 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: teep@ietfa.amsl.com
Delivered-To: teep@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F01B2C151095; Fri, 21 Jul 2023 15:55:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.855
X-Spam-Level:
X-Spam-Status: No, score=-0.855 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YkRZ2L8nWhUD; Fri, 21 Jul 2023 15:55:21 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31C60C14CF13; Fri, 21 Jul 2023 15:55:21 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 070F61ECFA2E; Fri, 21 Jul 2023 15:55:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, teep@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230721225521.070F61ECFA2E@rfcpa.amsl.com>
Date: Fri, 21 Jul 2023 15:55:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/teep/Oes8Z9QlDFL0U9SiRDSUY1AcViY>
Subject: [Teep] RFC 9397 on Trusted Execution Environment Provisioning (TEEP) Architecture
X-BeenThere: teep@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: A Protocol for Dynamic Trusted Execution Environment Enablement <teep.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teep>, <mailto:teep-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teep/>
List-Post: <mailto:teep@ietf.org>
List-Help: <mailto:teep-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teep>, <mailto:teep-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2023 22:55:26 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9397
Title: Trusted Execution Environment Provisioning (TEEP)
Architecture
Author: M. Pei,
H. Tschofenig,
D. Thaler,
D. Wheeler
Status: Informational
Stream: IETF
Date: July 2023
Mailbox: mingliang.pei@broadcom.com,
hannes.tschofenig@gmx.net,
dthaler@microsoft.com,
davewhee@amazon.com
Pages: 31
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-teep-architecture-19.txt
URL: https://www.rfc-editor.org/info/rfc9397
DOI: 10.17487/RFC9397
A Trusted Execution Environment (TEE) is an environment that enforces
the following: any code within the environment cannot be tampered
with, and any data used by such code cannot be read or tampered with
by any code outside the environment. This architecture document
discusses the motivation for designing and standardizing a protocol
for managing the lifecycle of Trusted Applications running inside
such a TEE.
This document is a product of the Trusted Execution Environment Provisioning Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC