PRE-RCT: Pre-Execution Authorization Receipt Format

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.¶

Table of Contents

1. Introduction

Pre-execution authorization systems require durable, verifiable records capturing action parameters, policy state, approver decisions, and attestation evidence at the moment of authorization. PRE-RCT defines a standard structure to support interoperability, auditing, compliance, and long-term integrity.¶

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. Design Goals

PRE-RCT is intended to:¶

* Provide strong non-repudiation.¶

* Bind action parameters to policy state.¶

* Support HAE attestation evidence.¶

* Support N-of-M approvals.¶

* Be portable across authorization systems.¶

4. Receipt Structure

PRE-RCT defines a structured object with required fields and optional domain extensions. The receipt MUST be integrity protected and cryptographically signed.¶

5. Required Fields

The following fields MUST be present:¶

receipt_id¶

action_hash¶

policy_hash¶

approver_identities¶

approver_signatures¶

timestamp¶

execution_token¶

hae_masking_profile_id¶

hae_attestation_token¶

context_snapshot (OPTIONAL)¶

6. Verification

Verifiers SHOULD:¶

* Validate structural integrity.¶

* Verify all digital signatures.¶

* Recompute and compare action_hash and policy_hash.¶

* Validate attestation tokens if present.¶

* Enforce timestamp bounds and replay protection.¶

7. IANA Considerations

This document has no IANA actions.¶

8. Security Considerations

PRE-RCT improves auditability and tamper-evidence but does not prevent collusion, coercion, or compromise below the firmware root of trust. Implementations MUST protect receipt confidentiality and integrity.¶

Authors' Addresses