I-D Action: draft-sparysh-pala-audit-00.txt

internet-drafts@ietf.org Thu, 03 September 2026 06:40 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-sparysh-pala-audit-00.txt
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <178841762658.661381.15023071686248660385@dt-datatracker-6669c7b496-s9mrn>
Date: Wed, 02 Sep 2026 23:40:26 -0700
Message-ID-Hash: 4DWZAVVAEUEJFTXCUTHTMVOJHVNT2YE4
Reply-To: internet-drafts@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/IRk-DJ1N3GGacx2-GxAK6x0uVPM>

Internet-Draft draft-sparysh-pala-audit-00.txt is now available.

   Title:   PALA-1: A Tamper-Evident Audit Record Format for Constrained and Disconnected Deployments
   Authors: Andrii Sparysh
            Oleksandr Verteletskyi
   Name:    draft-sparysh-pala-audit-00.txt
   Pages:   40
   Dates:   2026-09-02

Abstract:

   This document describes PALA-1, a compact binary record format for
   tamper-evident audit trails produced by AI inference runtimes and
   robotic control systems.  It is designed for a class of deployment
   defined by three constraints that hold together: the hardware is
   computationally modest and its cycles are reserved for the workload
   and the power budget rather than for the audit trail; no external
   witness is reachable, whether because policy forbids outbound contact
   or because the platform operates beyond connectivity, so a witness is
   unavailable by rule or by physics rather than by circumstance; and
   the right to verify the trail is separated from the right to read
   what it records.

   Records form an append-only hash chain.  Integrity verification
   requires no key material of any kind, inspects no record bodies, and
   costs one hash per record rather than one signature.  The format
   distinguishes three separately answerable questions -- internal
   consistency, completeness against an external anchor, and existence
   at a point in time against an external witness -- and states which of
   the three a given trail actually supports rather than implying all
   three.

   The format is frozen at version 1.0 and is described here as it is.
   This document presents an existing wire format; it does not revise
   one.  Where a deployment does permit an external witness, a chain
   head may be published to a transparency service such as that of the
   Supply Chain Integrity, Transparency, and Trust architecture (SCITT,
   RFC 9943); that path is described but is not part of the hashing
   contract.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-sparysh-pala-audit/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-sparysh-pala-audit-00

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts

I-D Action: draft-sparysh-pala-audit-00.txt internet-drafts