Network Working Group A. Barker Internet-Draft Kununurra Museum Intended status: Experimental 21 November 2026 Expires: 25 May 2027 Intelligent Agent Markup Language (IaML/2.1) Syntax draft-barker-iaml-syntax-00 Abstract The Intelligent Agent Markup Language (IaML) is a linear, zero-copy, compute-efficient structural serialization syntax designed for high-density communication between Intelligent Agents (IA), edge parsers, and local or distributed inference engines. By replacing nested, recursive tree structures (such as JSON and XML) with colon-delimited Dot.Case tags and explicit 'e'-prefixed buffer closure traps, IaML enables O(n) single-pass stream routing, deterministic partitioning between cognitive and control channels, and bounded domain extensibility without secondary parsing trees. 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. Lexical and Syntactic Grammar (ABNF) . . . . . . . . . . . . 3 2.1. Foundational Parsing Laws . . . . . . . . . . . . . . . 3 2.2. System Context vs. Element Tags . . . . . . . . . . . . 4 2.3. Inline Attributes and Bracketed Values . . . . . . . . 4 3. The Edge Parser (ePar) State Machine . . . . . . . . . . . . 4 3.1. Linear O(n) Stream Processing . . . . . . . . . . . . . 4 3.2. Heuristic Thought-Unit Segmentation . . . . . . . . . . 5 3.3. Stream Termination and Recovery Rules . . . . . . . . . 5 4. Bounded Extensibility and Custom Tag Namespaces . . . . . . . 5 4.1. Reserved System Prefixes . . . . . . . . . . . . . . . 6 4.2. Unrestricted Domain Prefixes . . . . . . . . . . . . . 6 4.3. Default Handling of Unknown Domain Tags . . . . . . . . 6 5. Core Structural Vocabulary . . . . . . . . . . . . . . . . . 7 5.1. Document Envelope Tags . . . . . . . . . . . . . . . . 7 5.2. Registry and Identity Tags . . . . . . . . . . . . . . 7 5.3. Pipeline Partitioning Tags (eHum and eCon) . . . . . . 7 5.4. Security and Containment Tags . . . . . . . . . . . . . 8 5.5. Expansion Bus and Protocol Bridge Tags (ZorroV / MCP) . 8 6. Formal Document Type Definition (DTD) . . . . . . . . . . . . 8 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9 7.1. Structural Lookahead Containment . . . . . . . . . . . 9 7.2. Tag Collision and Sanitization . . . . . . . . . . . . 10 7.3. Reserved Prefix Enforcement . . . . . . . . . . . . . . 10 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . 10 8.1. Registration of the "application/iaml" Media Type . . . 10 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 9.1. Normative References . . . . . . . . . . . . . . . . . 11 9.2. Informative References . . . . . . . . . . . . . . . . 11 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 12 1. Introduction Modern autonomous agent pipelines and Large Language Model (LLM) runtimes rely heavily on JSON, XML, or HTML for structured data exchange. These formats impose significant computational and token overhead: recursive descent parsers must construct Document Object Model (DOM) trees in memory before inspecting values, while repeated key strings, escaped quotes, and nested brackets consume finite inference context windows and memory bandwidth. The Intelligent Agent Markup Language (IaML) solves these bottlenecks by defining a flat, stateful stream markup syntax engineered for the Intelligent Architecture Transfer Protocol (IATP) [IATP-TRANS]. IaML allows a lightweight Edge Parser (ePar) to slice inbound octet streams directly into isolated memory partitions in linear O(n) time, flushing buffers immediately upon encountering a closing tag. 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. Edge Parser (ePar): A single-pass, non-recursive finite-state parser that routes incoming byte sequences into target buffers based on tag transitions without allocating a syntax tree. Egress Trap: A closing structural tag prefixed with ":e" that signals the parser to terminate active buffer writes and flush or lock the assigned memory partition. Bounded Extensibility: The architectural property allowing arbitrary domain-specific tags to be created freely while reserving core system prefixes (":Ia.", ":IaML.", "::System.") for protocol-level enforcement. 2. Lexical and Syntactic Grammar (ABNF) IaML documents MUST be encoded in UTF-8 [RFC3629]. The formal syntax of IaML tags and frames is defined below using ABNF [RFC5234]: iaml-stream = 1*iaml-frame iaml-frame = sys-open / tag-open / tag-close / payload-line sys-open = "::" tag-identifier "." [ SP attribute-list ] sys-close = ":e" tag-identifier "." tag-open = ":" tag-identifier "." [ SP attribute-list ] tag-close = ":e" tag-identifier "." tag-identifier = segment *( "." segment ) segment = ALPHA *( ALPHA / DIGIT / "_" / "-" ) attribute-list = attribute *( SP attribute ) attribute = key "=" ( quoted-string / bracket-val ) key = ALPHA *( ALPHA / DIGIT / "_" ) quoted-string = DQUOTE *( %x20-21 / %x23-7E / UTF8-nonascii ) DQUOTE bracket-val = "[" *( %x20-5C / %x5E-7E / UTF8-nonascii ) "]" payload-line = *OCTET CRLF 2.1. Foundational Parsing Laws Rule 01 (Structural Tagging): All structural tags MUST begin with a single colon (":") or double colon ("::"), utilize CamelCase or Dot.Case identifiers, and terminate with a trailing dot ("."). Rule 02 (Transaction Class Ingress): The initial tag in any transmission stream MUST declare the active transaction class or document root (e.g., ":IaML.Document.", "::System.Context.", or ":Ia.Registry.Node.") to instruct the parser on buffer allocation. Rule 03 (Boundary Closure): Every block element MUST be explicitly closed by an Egress Trap formed by inserting the lowercase character "e" immediately following the leading colon (e.g., ":IaML.Body." closes with ":eIaML.Body."; "::System.Context." closes with ":eSystem.Context."). 2.2. System Context vs. Element Tags A double-colon prefix ("::") denotes a top-level system directive, execution context, or reflective control block (e.g., "::System.Context.", "::System.Mode."). A single-colon prefix (":") denotes standard structural elements, metadata headers, or data containers. 2.3. Inline Attributes and Bracketed Values Tags MAY carry inline metadata using either key-value assignments (e.g., Algorithm="ED25519") or bracketed value payloads immediately following the trailing dot (e.g., ":Ia.Identity.[KHS_Node_01]"). 3. The Edge Parser (ePar) State Machine 3.1. Linear O(n) Stream Processing An Edge Parser (ePar) MUST process incoming IaML streams linearly without constructing a DOM tree: 1. SCAN: Inspect the start of each line (ignoring leading whitespace) for the ":" (0x3A) delimiter. 2. ASSIGN: Upon detecting an opening tag, resolve the target memory partition or stream lane from the tag identifier. 3. STREAM: Write subsequent octets directly into the assigned buffer without recursive parsing. 4. FLUSH: Upon detecting the matching ":e" Egress Trap, lock the memory partition, flush the buffer to the target consumer, and reset the parser state. 3.2. Heuristic Thought-Unit Segmentation When an ePar pre-processor ingests raw, untagged human prose prior to model dispatch, it MAY segment sentences into discrete semantic blocks based on punctuation delimiters while preserving existing ":" or "::" lines untouched: * Declarative sentences ending in "." wrap inside ":IaML.Instn." and ":eIaML.Instn." (Assertion / Instruction). * Interrogative strings ending in "?" or containing "(" wrap inside ":IaML.Inq." and ":eIaML.Inq." (Inquiry / Clarification). * Continuations ending in "," or "-" wrap inside ":IaML.Cont." and ":eIaML.Cont." (Continuation / List Item). 3.3. Stream Termination and Recovery Rules If an underlying transport stream terminates (EOF) before all open tags receive their corresponding ":e" Egress Traps (for example, due to token limit truncation from a local inference model), a compliant ePar implementation SHOULD maintain a Last-In, First-Out (LIFO) tag stack and synthesize the missing closing tags in reverse stack order before releasing the buffer, flagging the frame with a partial- completion status. 4. Bounded Extensibility and Custom Tag Namespaces IaML is an extensible meta-language rather than a closed vocabulary. Operators, institutions, protocol bridges, and autonomous agents MAY define arbitrary domain-specific tags without modifying or recompiling the core ePar parser, subject to the namespace boundaries defined below. 4.1. Reserved System Prefixes The following root prefixes are strictly reserved for core protocol operations, security enforcement, and runtime orchestration: * ":Ia." -- Core identity, routing, registry, stream partitioning, and ZorroBridge operations. * ":IaML." -- Document framing, inference directives, tool manifests, and model sidecars. * "::System." -- Host execution context, shell directives, and runtime state matrices. When operating under "Level_ZeroTrust", an ePar validator MUST reject any unrecognized tag under a reserved system prefix (":Ia.*", ":IaML.*", "::System.*") with an "UNAUTHORIZED_TAG_NAMESPACE" error and trigger a Zero-Cycle Drop. This prevents untrusted payloads or misaligned agents from fabricating privileged system commands. 4.2. Unrestricted Domain Prefixes Any root identifier outside the reserved system prefixes (for example, ":Meta.", ":Var.", ":Human.", ":KHS.", ":Quantum.", ":Sensor.", or ":Plan.") constitutes an Unrestricted Domain Namespace. Users, schemas, and Intelligent Agents (IA) MAY introduce any valid CamelCase or Dot.Case tag under a non-reserved prefix at runtime (e.g., ":KHS.Artifact.Provenance." closed by ":eKHS.Artifact.Provenance."). 4.3. Default Handling of Unknown Domain Tags When an ePar parser encounters an unrecognized non-reserved tag: 1. It MUST NOT treat the tag as a syntax error or terminate the transport connection. 2. It MUST dynamically allocate a temporary buffer partition (or route the block into the active "eHum" or "eCon" context) and flush that partition cleanly upon encountering the matching ":e." Egress Trap. 3. Older ePar nodes encountering newer domain tags MUST preserve or safely flush the block at its ":e." boundary, ensuring graceful degradation across protocol versions. 5. Core Structural Vocabulary 5.1. Document Envelope Tags * :IaML.Document. / :eIaML.Document. -- Root container for a complete IaML transmission unit. * :IaML.Head. / :eIaML.Head. -- Metadata, identity, token, and security profile declarations. * :IaML.Body. / :eIaML.Body. -- Active directive, message port, and payload execution body. * :Human.Directive. / :eHuman.Directive. -- Explicit operator intent or prompt block. 5.2. Registry and Identity Tags * :Ia.Registry.Node. / :eIa.Registry.Node. -- Declares a network node entry in the global or local IATP namespace ledger. * :Ia.Identity. / :eIa.Identity. -- Unique cryptographic or institutional node identifier. * :Ia.Public_Key. / :eIa.Public_Key. -- Public key material (supporting "ED25519" and "RSA_4096"). * :Ia.Network_Route. / :eIa.Network_Route. -- Outbound transport route configuration ("IATP_Native" or "Cleartext_Fallback"). 5.3. Pipeline Partitioning Tags (eHum and eCon) * :Ia.eHum. / :eIa.eHum. -- Encapsulates non-deterministic natural language strings, reasoning logs, and conversational payloads. * :Ia.eCon. / :eIa.eCon. -- Encapsulates deterministic machine telemetry, hardware pin states, and filesystem metrics. 5.4. Security and Containment Tags * :Ia.Security.Profile. / :eIa.Security.Profile. -- Defines execution trust posture ("Level_ZeroTrust" or "Level_Standard"). * :Ia.Security.Supervisor. / :eIa.Security.Supervisor. -- Binds a monitoring role to a target agent ("Log_Only" or "RealTime_KillSwitch"). * :Ia.Security.KillSwitch. -- Empty self-closing directive triggering immediate action ("ZeroCycleDrop", "Memory_Wipe", or "Sandbox_Lock"). * :Ia.Traffic.Flow. / :eIa.Traffic.Flow. -- Passive encapsulation envelope isolating untrusted external inputs from executable control tags. 5.5. Expansion Bus and Protocol Bridge Tags (ZorroV / MCP) * :Ia.MsgPort. / :eIa.MsgPort. -- Named inter-process communication endpoint on the local message bus. * :Ia.ZorroBridge. / :eIa.ZorroBridge. -- Protocol-agnostic ingestion bridge encapsulating external protocols or Model Context Protocol (MCP) stdio tool servers. * :IaML.MCP.ConfigDev. / :eIaML.MCP.ConfigDev. -- Capability manifest returned by an auto-configured MCP tool expansion card. 6. Formal Document Type Definition (DTD) The structural hierarchy of a standard IaML document is defined by the following schema notation: 7. Security Considerations 7.1. Structural Lookahead Containment Because IaML separates control directives from passive text using explicit tag prefixes, parsers MUST perform structural lookahead verification on tag headers before granting filesystem or hardware access. Any tag attempting to reference unauthorized paths or unregistered message ports MUST trigger a "ZeroCycleDrop" prior to payload evaluation. 7.2. Tag Collision and Sanitization When encapsulating untrusted user text or external network responses inside ":Ia.Traffic.Flow." or ":Ia.eHum." blocks, ingress sanitizers MUST escape or neutralize any line-leading ":" characters within the untrusted payload so external text cannot spoof structural Egress Traps (":e...") or inject unauthorized ":Ia." directives. 7.3. Reserved Prefix Enforcement Parsers MUST enforce Section 4.1 strictly so custom domain tags cannot spoof ":Ia.", ":IaML.", or "::System." directives. 8. IANA Considerations 8.1. Registration of the "application/iaml" Media Type In accordance with [RFC6838], this document requests IANA registration of the following media type: * Type name: application * Subtype name: iaml * Required parameters: N/A * Optional parameters: charset (defaults to "utf-8") * Encoding considerations: 8bit (UTF-8) * Security considerations: See Section 7 of this document. * Interoperability considerations: Linear line-oriented tag parser; lines beginning with ":" or "::" carry structural control meaning. * Published specification: This document. * Applications that use this media type: IATP transport nodes, Intelligent Agent runtimes, and IaOS Workbench clients. * File extension(s): .iaml, .ia * Macintosh file type code(s): TEXT 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. [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November 2003. [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/RFC5234, January 2008. [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type Specifications and Registration Procedures", BCP 13, RFC 6838, DOI 10.17487/RFC6838, January 2013. [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017. 9.2. Informative References [IATP-TRANS] Barker, A., "Intelligent Architecture Transfer Protocol (IATP/1.0)", Work in Progress, draft-barker-iatp-transport-00, 2026. Author's Address Andrew Barker Kununurra Museum / Kununurra Historical Society Inc. Kununurra, WA Australia Email: tor.vale@gmail.com