Network Working Group A. Barker Internet-Draft Kununurra Museum Intended status: Experimental 21 November 2026 Expires: 25 May 2027 Intelligent Architecture Transfer Protocol (IATP/1.0) draft-barker-iatp-transport-00 Abstract The Intelligent Architecture Transfer Protocol (IATP) is a lightweight, stateful, zero-copy transport protocol designed for deterministic communication between Intelligent Agents (IA), local inference runtimes, hardware edge controllers, and federated knowledge nodes. Operating natively over TCP port 7027 (cleartext local/intranet) and TLS port 443 (federated), IATP pairs a three- phase T-Pipe multiplexer with Length-Prefix Chunk Framing and the Intelligent Agent Markup Language (IaML) to achieve O(n) single-pass stream routing without head-of-line blocking, recursive tree allocation, or patent-based encumbrances. 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 25 May 2027. Copyright Notice 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology and Requirements Language . . . . . . . . . 2 2. URI Scheme and Addressing ("iatp://") . . . . . . . . . . . . 3 2.1. URI Syntax (ABNF) . . . . . . . . . . . . . . . . . . . 3 2.2. Transport Execution Modes . . . . . . . . . . . . . . . 3 2.3. Local vs. Federated Namespace Zones . . . . . . . . . . 4 3. Connection Lifecycle and Handshake . . . . . . . . . . . . . 4 3.1. Port Allocation and TLS Upgrade . . . . . . . . . . . . 4 3.2. Capability and Security Posture Negotiation . . . . . . 4 4. Three-Phase T-Pipe Multiplexing and Wire Framing . . . . . . 5 4.1. Phase 1: Target Lane Addressing . . . . . . . . . . . . 5 4.2. Phase 2: Length-Prefix Chunk Framing (Zero-Copy) . . . 5 4.3. Phase 3: Egress Closure and State Reset . . . . . . . . 6 4.4. Legacy Unframed Stream Fallback (Colon-Stuffing) . . . 6 5. Deterministic Flow Control and Loop Containment . . . . . . . 7 5.1. The Dodo Guard (Recursive Cycle Interception) . . . . . 7 5.2. Zero-Cycle Drop Enforcement . . . . . . . . . . . . . . 7 6. Protocol Bridging (ZorroV / MCP) . . . . . . . . . . . . . . 7 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8 7.1. Transport Encryption and Node Authentication . . . . . 8 7.2. Buffer Alignment and Integer Overflow Protection . . . 8 7.3. Containment of Untrusted Payloads . . . . . . . . . . . 8 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 8.1. Registration of the "iatp" URI Scheme . . . . . . . . . 9 8.2. Registration of TCP Port 7027 . . . . . . . . . . . . . 9 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 9.1. Normative References . . . . . . . . . . . . . . . . . 10 9.2. Informative References . . . . . . . . . . . . . . . . 10 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 11 1. Introduction Autonomous multi-agent systems and edge inference runtimes require a transport layer optimized for low-latency, deterministic memory routing. Conventional web protocols such as HTTP/1.1, HTTP/2, and JSON-RPC over WebSockets introduce substantial framing overhead, redundant header serialization, and recursive payload parsing before data can be dispatched to inference engines or hardware actuators. The Intelligent Architecture Transfer Protocol (IATP) provides a minimalist, stateful wire transport designed specifically to carry Intelligent Agent Markup Language (IaML) streams [IAML-SYNTAX] and raw binary tensor or telemetry bursts. By decoupling stream routing headers from opaque binary chunks via Length-Prefix Chunk Framing, IATP allows an Edge Parser (ePar) to map network octets directly into shared-memory or DMA target buffers in O(n) linear time. 1.1. Terminology and 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. T-Pipe Multiplexer: A stateful wire framing mechanism that partitions a single transport connection into isolated logical lanes using three sequential phases (Address, Burst, Closure). Burst Frame: A length-prefixed payload chunk within Phase 2 that carries opaque octets without per-byte delimiter scanning. Dodo Guard: A deterministic transport watchdog that terminates connections exhibiting unbounded recursive agent loops. 2. URI Scheme and Addressing ("iatp://") 2.1. URI Syntax (ABNF) Endpoints in an IATP network are identified using the "iatp" URI scheme, defined in ABNF [RFC5234] conforming to [RFC3986]: iatp-uri = "iatp://" authority "/" mode "/" node "/" target authority = host [ ":" port ] mode = "exec" / "blit" / "cop" / "auto" node = 1*( ALPHA / DIGIT / "." / "_" / "-" ) target = 1*( ALPHA / DIGIT / "." / "_" / "-" / "/" ) 2.2. Transport Execution Modes The path segment instructs the receiving node on how to schedule and allocate memory for the incoming stream: * "exec" -- Zero-copy shared-memory pointer passing for local inter-process agent loops and inference pipelines. * "blit" -- Contiguous bit-block matrix routing optimized for raw tensor weights, embeddings, and high-frequency sensor telemetry. * "cop" -- Deterministic WAIT/MOVE copper-list scheduling for synchronized multi-step hardware or agent execution. * "auto" -- AutoConfig discovery mode for hot-plugging sub-agents and Model Context Protocol (MCP) tool servers via ZorroV. 2.3. Local vs. Federated Namespace Zones * Local / Air-Gapped Zone: Authorities such as "local" or "dh0.archive" operate on isolated host or intranet fabrics with zero external DNS or ledger dependencies. * Federated Zone: Global authorities utilize institutional TLDs ("glam", "gov", "edu", "org", "ind", "corp") authenticated via cryptographic node keys ("ED25519" or "RSA_4096"). 3. Connection Lifecycle and Handshake 3.1. Port Allocation and TLS Upgrade IATP endpoints MUST listen on TCP port 7027 for local or air-gapped intranet links where physical or VLAN isolation is guaranteed. For all federated or wide-area connections, IATP MUST operate over TLS 1.3 [RFC9846] on TCP port 443 (or port 7027 with explicit STARTTLS upgrade). 3.2. Capability and Security Posture Negotiation Immediately upon establishing a transport connection, the initiator MUST transmit an IaML handshake envelope declaring its node identity, supported execution modes, and security profile ("Level_ZeroTrust" or "Level_Standard"). The responder MUST reply with a matching ":Ia.Registry.Node." acknowledgment before any T-Pipe data bursts are transmitted. 4. Three-Phase T-Pipe Multiplexing and Wire Framing To multiplex structured IaML control tags and arbitrary binary or text payloads over a single TCP/TLS stream without head-of-line blocking, IATP uses a deterministic three-phase T-Pipe state machine. 4.1. Phase 1: Target Lane Addressing The sender initiates a multiplexed transfer by emitting a single Phase 1 routing header terminated by CRLF: :RouteTo.. CRLF Upon reading the trailing dot and CRLF, the receiving Edge Parser (ePar) resolves to an active memory partition or message port ("MsgPort") and transitions from tag-scanning mode into Phase 2 Burst mode. 4.2. Phase 2: Length-Prefix Chunk Framing (Zero-Copy) Because binary payloads (such as model tensors, images, or raw text logs) may contain arbitrary byte sequences -- including the literal ASCII characters ":eBurst." -- Phase 2 MUST NOT rely on delimiter scanning. Instead, Phase 2 MUST use Length-Prefix Chunk Framing: 1. Chunk Header: Each data chunk in Phase 2 MUST begin with the ASCII header ":Burst. CRLF", where is an unsigned base-10 integer (0 to 4294967295) specifying the exact number of payload octets immediately following the CRLF. 2. Opaque Payload Transfer: Upon parsing , the receiving ePar parser MUST read exactly raw octets directly into the target DMA or shared-memory buffer without scanning for IaML tags or delimiters. Any occurrence of ":eBurst." inside those octets MUST be treated as opaque payload data. 3. Dynamic Streaming: A sender MAY emit multiple sequential ":Burst. " chunks within a single Phase 2 session as inference tokens or telemetry buffers fill. 4. Terminal Chunk: A zero-length chunk header (":Burst. 0 CRLF") MUST be emitted to signal the completion of Phase 2 payload octets. 4.3. Phase 3: Egress Closure and State Reset Immediately following ":Burst. 0 CRLF", the sender MUST emit the Phase 3 Egress Trap: :eBurst. CRLF Upon receiving ":eBurst. CRLF", the receiver locks and flushes the target memory partition to its consumer and resets the T-Pipe multiplexer back to standard Phase 1 / IaML tag-scanning mode. Example wire sequence: :RouteTo.khs.Collection.Photos. :Burst. 65536 <65536 raw octets> :Burst. 1024 <1024 raw octets> :Burst. 0 :eBurst. 4.4. Legacy Unframed Stream Fallback (Colon-Stuffing) When bridging an unframed legacy byte stream via ZorroBridge where chunk sizes cannot be determined prior to emission, implementations MAY negotiate Colon-Doubling Octet-Stuffing: * Sender Rule: Any occurrence of ":eBurst." at offset 0 of the payload or immediately following CRLF/LF MUST be prepended with an additional colon ("::eBurst."). * Receiver Rule: An unescaped ":eBurst." at offset 0 or after a newline terminates Phase 2; any leading "::eBurst." has one colon stripped before writing to the target buffer. 5. Deterministic Flow Control and Loop Containment 5.1. The Dodo Guard (Recursive Cycle Interception) Autonomous agents operating in peer-to-peer loops risk entering unbounded self-prompting cycles. Compliant IATP nodes MUST maintain a per-session cycle counter ("DodoCounter"). If a connection executes more than 10 sequential nested request-response cycles without an external state confirmation or operator reset, the node MUST trigger a "Dodo.Drop" intercept, flush active buffers, and close the transport socket immediately. 5.2. Zero-Cycle Drop Enforcement Under "Level_ZeroTrust", if a Phase 1 ":RouteTo." header references an unregistered target lane, attempts path traversal ("../"), or violates reserved IaML prefixes, the receiver MUST execute a "ZeroCycleDrop" -- terminating the connection immediately without allocating payload buffers or invoking downstream inference models. 6. Protocol Bridging (ZorroV / MCP) IATP nodes MAY expose external tools and Model Context Protocol (MCP) servers over the local bus using ZorroV AutoConfig expansion cards. Bridged MCP servers MUST execute as isolated child processes over standard I/O ("stdio") encapsulated inside ":Ia.ZorroBridge." frames so external tool traffic inherits IATP loop containment and buffer isolation without opening extra network sockets. 7. Security Considerations 7.1. Transport Encryption and Node Authentication Cleartext operation on TCP port 7027 MUST be restricted to loopback interfaces or physically isolated local networks. All federated deployments MUST enforce TLS 1.3 [RFC9846] and verify peer node identities using ED25519 or RSA_4096 signatures during the Section 3.2 handshake. 7.2. Buffer Alignment and Integer Overflow Protection Parsers processing ":Burst. " headers MUST validate that does not exceed the receiver's configured maximum frame quota (default 16 MiB) prior to buffer allocation, rejecting oversized or malformed length headers with a "ZeroCycleDrop" to prevent integer overflow or memory exhaustion attacks. 7.3. Containment of Untrusted Payloads Data ingested from external networks or unverified peers MUST be routed into passive ":Ia.Traffic.Flow." lanes [IAML-SYNTAX] and MUST NOT be granted direct access to "::System." or ":Ia.MsgPort." control channels. 8. IANA Considerations 8.1. Registration of the "iatp" URI Scheme In accordance with [RFC7595], this document requests IANA registration of the provisional URI scheme "iatp": * Scheme name: iatp * Status: Provisional * Applications/protocols that use this scheme: Intelligent Architecture Transfer Protocol (IATP/1.0) nodes and IaOS clients. * Contact: Andrew Barker * Change controller: Andrew Barker 8.2. Registration of TCP Port 7027 In accordance with [RFC6335], this document requests IANA assignment of TCP port 7027: * Service Name: iatp * Transport Protocol: TCP * Assignee: Andrew Barker * Contact: Andrew Barker * Description: Intelligent Architecture Transfer Protocol * Reference: This document 9. References 9.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997. [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, DOI 10.17487/RFC3986, January 2005. [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/RFC5234, January 2008. [RFC6335] Cotton, M., Eggert, L., Touch, J., Westerlund, M., and S. Cheshire, "Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry", BCP 165, RFC 6335, DOI 10.17487/RFC6335, August 2011. [RFC7595] Thaler, D., Ed., Hansen, T., and T. Hardie, "Guidelines and Registration Procedures for URI Scheme Names", BCP 35, RFC 7595, DOI 10.17487/RFC7595, June 2015. [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017. [RFC9846] Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.3", RFC 9846, DOI 10.17487/RFC9846, 2026. 9.2. Informative References [IAML-SYNTAX] Barker, A., "Intelligent Agent Markup Language (IaML/2.1) Syntax", Work in Progress, draft-barker-iaml-syntax-00, 2026. Author's Address Andrew Barker Kununurra Museum / Kununurra Historical Society Inc. Kununurra, WA Australia Email: tor.vale@gmail.com