[フレーム] Skip to main content
Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript. Please enable Javascript for full functionality.

High-Assurance Execution Environment (HAE) for Secure Approval
draft-madaras-high-assurance-exec-00

This document is an Internet-Draft (I-D). Anyone may submit an I-D to the IETF. This I-D is not endorsed by the IETF and has no formal standing in the IETF standards process.
Document Type Active Internet-Draft (individual)
Authors tom madaras , Pat Estis
Last updated 2025年12月03日
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date (None)
Responsible AD (None)
Send notices to (None)
Email authors IPR References Referenced by Nits Search email archive
draft-madaras-high-assurance-exec-00
Network Working Group T. Madaras
Internet-Draft P. Estis
Intended status: Experimental GuardSuite, VXMSecure
Expires: 6 June 2026 3 December 2025
 High-Assurance Execution Environment (HAE) for Secure Approval
 draft-madaras-high-assurance-exec-00
Abstract
 This document specifies the High-Assurance Execution Environment
 (HAE), a trusted, ephemeral approval environment designed to protect
 the authorization of high-risk digital and physical actions.
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 6 June 2026.
Copyright Notice
 Copyright (c) 2025 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 Revised BSD License text as
 described in Section 4.e of the Trust Legal Provisions and are
 provided without warranty as described in the Revised BSD License.
Madaras & Estis Expires 6 June 2026 [Page 1]
Internet-Draft HAE December 2025
Table of Contents
 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 2
 3. Security Considerations . . . . . . . . . . . . . . . . . . . 2
 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2
 5. Normative References . . . . . . . . . . . . . . . . . . . . 2
 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 2
1. Introduction
 The High-Assurance Execution Environment (HAE) provides an isolated,
 attestation-backed approval environment for high-risk actions such as
 financial transfers, cloud administrative operations, industrial
 control system commands, and AI-initiated operations.
2. Requirements Language
 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
 "OPTIONAL" in this document are to be interpreted as described in BCP
 14 ([RFC2119], [RFC8174]) when, and only when, they appear in all
 capitals, as shown here.
3. Security Considerations
 This document introduces no security considerations beyond those
 inherent in isolated execution and attestation systems.
4. IANA Considerations
 This document has no IANA actions.
5. Normative References
 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
 Requirement Levels", BCP 14, RFC 2119, March 1997,
 <https://www.rfc-editor.org/rfc/rfc2119>.
 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
 2119 Key Words", BCP 14, RFC 8174, May 2017,
 <https://www.rfc-editor.org/rfc/rfc8174>.
Authors' Addresses
Madaras & Estis Expires 6 June 2026 [Page 2]
Internet-Draft HAE December 2025
 Tom Madaras
 GuardSuite, VXMSecure
 Hollywood, FL
 United States of America
 Email: tom@vxmsecure.com
 Pat Estis
 GuardSuite, VXMSecure
 Houston, TX
 United States of America
 Email: pat.estis@gmail.com
Madaras & Estis Expires 6 June 2026 [Page 3]

AltStyle によって変換されたページ (->オリジナル) /