<?xml version="1.0" encoding="UTF-8"?>
<rfc version="3"
     ipr="trust200902"
     docName="draft-shuliak-sip-zero-egress-00"
     submissionType="IETF"
     category="info"
     tocInclude="true"
     sortRefs="true"
     symRefs="true">
  <front>
    <title abbrev="SIP-1 Zero-Egress Isolation">Shuliak Isolation Protocol (SIP-1): Stateless Format-Preserving Pseudonymization and AST Quarantine for Local AI Agent Transports</title>
    <author initials="D." surname="Shuliak" fullname="Dmitrii Shuliak">
      <organization>SHULIAK CORP</organization>
      <address>
        <postal>
          <street>17 Pirosmani St.</street>
          <city>Batumi</city>
          <code>6000</code>
          <country>Georgia</country>
        </postal>
        <email>hq@shuliak.dev</email>
        <uri>https://shuliak.dev</uri>
      </address>
    </author>
    <date year="2026" month="November" day="15"/>
    <area>Security</area>
    <workgroup>Network Working Group</workgroup>
    <keyword>MCP</keyword>
    <keyword>Format-Preserving Encryption</keyword>
    <keyword>FF1</keyword>
    <keyword>Zero-Egress</keyword>
    <abstract>
      <t>Autonomous AI agents and Model Context Protocol (MCP) servers frequently execute over local standard input/output (stdio) pipes outside enterprise network inspection perimeters. Naive redaction of sensitive credentials with static placeholders invalidates downstream Luhn payment card and ISO-7064 IBAN schema validators, while raw payload forwarding exposes regulated data. This document specifies the Shuliak Isolation Protocol (SIP-1), a deterministic, zero-egress security layer combining stateless Format-Preserving Encryption (FF1), Abstract Syntax Tree (AST) JSON-RPC payload quarantine, and detached cryptographic schema locks.</t>
    </abstract>
  </front>
  <middle>
    <section anchor="intro">
      <name>Introduction and Problem Statement</name>
      <t>Local agentic tool transports exchange JSON-RPC 2.0 messages directly between host applications and subprocesses over stdio. Cloud Data Loss Prevention (DLP) gateways cannot inspect these local pipes without breaking zero-egress confidentiality requirements.</t>
      <t>SIP-1 defines an inline, client-side cryptographic isolation boundary grounded in <xref target="NIST-FF1"/> and documented in the reference architecture <xref target="SIP1-ZENODO"/>. Sensitive tokens are bijectively mapped to format-valid synthetic twins in volatile memory before crossing tool or model boundaries.</t>
    </section>
    <section anchor="conventions">
      <name>Conventions and Terminology</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here.</t>
    </section>
    <section anchor="architecture">
      <name>Deterministic AST Quarantine and FF1 Bijection</name>
      <t>Before forwarding any JSON-RPC 2.0 request or tool output, a compliant SIP-1 interceptor <bcp14>MUST</bcp14> enforce two sequential local gates:</t>
      <ul>
        <li><t>Gate 1 (AST Quarantine): Reject payloads containing Plane-14 Unicode tag characters (U+E0000..U+E007F), unauthorized path traversal sequences targeting host credentials, or unpinned tool schema mutations.</t></li>
        <li><t>Gate 2 (Checksum-Invariant FF1 Bijection): Transform payment card numbers (PAN), bank accounts (IBAN), and API secrets using AES-256 in FF1 mode <xref target="NIST-FF1"/> with domain-separated tweaks, preserving Luhn and ISO-7064 MOD-97 check digits without persistent plaintext vaults.</t></li>
      </ul>
      <t>Implementations <bcp14>MUST NOT</bcp14> use the withdrawn FF3 or FF3-1 modes due to known small-domain cryptanalytic weaknesses.</t>
    </section>
    <section anchor="envelope">
      <name>Canonical Schema Lock and Attestation Envelope</name>
      <t>To prevent post-approval tool definition tampering (Rug Pull attacks) and support tamper-evident compliance telemetry, tool schemas and audit records <bcp14>MUST</bcp14> be canonicalized using JSON Canonicalization Scheme (JCS) <xref target="RFC8785"/> prior to SHA-256 hashing and signed using Ed25519 <xref target="RFC8032"/>.</t>
      <sourcecode type="json"><![CDATA[
{
  "sip_version": "1.0",
  "mode": "FF1-AES256-ZERO-EGRESS",
  "schema_jcs_sha256": "e3b0c44298fc1c149afbf4c8996fb924",
  "merkle_prev": "8f434346648f6b96df89dda901c5176b",
  "ed25519_sig": "base64url_detached_64byte_signature"
}
]]></sourcecode>
    </section>
    <section anchor="iana">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions.</t>
    </section>
    <section anchor="security">
      <name>Security Considerations</name>
      <t>Ephemeral FF1 keys <bcp14>MUST</bcp14> be generated via an operating system cryptographically secure pseudorandom number generator (CSPRNG) of at least 256 bits. When long-term tamper-evident audit chains are maintained alongside regulatory erasure obligations, per-identifier random keys <bcp14>SHOULD</bcp14> be isolated so that cryptographic key destruction renders synthetic twins irreversible against dictionary enumeration while preserving outer hash-chain integrity.</t>
    </section>
  </middle>
  <back>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author initials="S." surname="Bradner" fullname="S. Bradner"/>
            <date year="1997" month="March"/>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author initials="B." surname="Leiba" fullname="B. Leiba"/>
            <date year="2017" month="May"/>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
        <reference anchor="RFC8032" target="https://www.rfc-editor.org/info/rfc8032">
          <front>
            <title>Edwards-Curve Digital Signature Algorithm (EdDSA)</title>
            <author initials="S." surname="Josefsson" fullname="S. Josefsson"/>
            <author initials="I." surname="Liusvaara" fullname="I. Liusvaara"/>
            <date year="2017" month="January"/>
          </front>
          <seriesInfo name="RFC" value="8032"/>
          <seriesInfo name="DOI" value="10.17487/RFC8032"/>
        </reference>
        <reference anchor="RFC8785" target="https://www.rfc-editor.org/info/rfc8785">
          <front>
            <title>JSON Canonicalization Scheme (JCS)</title>
            <author initials="A." surname="Rundgren" fullname="A. Rundgren"/>
            <author initials="B." surname="Jordan" fullname="B. Jordan"/>
            <author initials="S." surname="Erdtman" fullname="S. Erdtman"/>
            <date year="2020" month="June"/>
          </front>
          <seriesInfo name="RFC" value="8785"/>
          <seriesInfo name="DOI" value="10.17487/RFC8785"/>
        </reference>
        <reference anchor="NIST-FF1" target="https://doi.org/10.6028/NIST.SP.800-38Gr1">
          <front>
            <title>Recommendation for Block Cipher Modes of Operation: Methods for Format-Preserving Encryption</title>
            <author initials="M." surname="Dworkin" fullname="Morris Dworkin">
              <organization>National Institute of Standards and Technology</organization>
            </author>
            <date year="2019" month="February"/>
          </front>
          <seriesInfo name="NIST Special Publication" value="800-38G Revision 1"/>
          <seriesInfo name="DOI" value="10.6028/NIST.SP.800-38Gr1"/>
        </reference>
      </references>
      <references>
        <name>Informative References</name>
        <reference anchor="SIP1-ZENODO" target="https://doi.org/10.5281/zenodo.24159380">
          <front>
            <title>Shuliak Isolation Protocol (SIP-1): Stateless Checksum-Invariant Format-Preserving Pseudonymization and AST Sanitization for Autonomous AI Transports</title>
            <author initials="D." surname="Shuliak" fullname="Dmitrii Shuliak">
              <organization>SHULIAK CORP</organization>
            </author>
            <date year="2026" month="November"/>
          </front>
          <seriesInfo name="DOI" value="10.5281/zenodo.24159380"/>
        </reference>
      </references>
    </references>
  </back>
</rfc>
