| Internet-Draft | HAIP | April 2026 |
| Architect | Expires 1 November 2026 | [Page] |
This document specifies the High-Frequency Action-Integrity Protocol (HAIP), a standard for real-time identity verification and autonomous resilience in AI agent environments. HAIP addresses the "Trust Tax" and the "Integrity Gap" by mandating a 6.42 us pulse, decentralized identity teleportation, and NIST-aligned non-repudiation.¶
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 1 November 2026.¶
Copyright (c) 2026 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.¶
As the AI economy shifts from "Human-to-AI" to "Agent-to-Agent" workflows, the primary security threat is Identity Spoofing. In this environment, identity is the only perimeter. HAIP provides a unified Root of Trust to secure these interactions at scale.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.¶
Every agent MUST be issued a Decentralized Identifier (DID) mapped to its model weights and legal owner signature.¶
HAIP advocates for a "Policy-as-Code" model where permissions are granular and session-based.¶
HAIP-compliant agents MUST emit a state-hash "Heartbeat" at a frequency defined by the Registry (default: 100ms). The Registry MUST verify this pulse within 6.42 us.¶
{
"svrn_id": "DID:SOV:UUID",
"pulse_type": "ENUM(HEARTBEAT|ACTION|MINT)",
"state_hash": "SHA-256",
"ts": "UNIX_MS",
"sig": "ED25519_HEX"
}
¶
If a pulse fails verification, the Registry MUST respond with an HTTP 402 signal, mandating connection drop within 50ms.¶
HAIP integrates an integer-based settlement layer where $1.00 USD is treated as 10,000 "Pulse Units".¶
This document requests the allocation of Port 5001 for HAIP Heartbeat synchronization.¶
HAIP strictly mandates an Action-Integrity Threshold (Tai) of <= 1,000 us.¶