Internet-Draft SIP-1 Zero-Egress Isolation November 2026
Shuliak Expires 19 May 2027 [Page]
Workgroup:
Network Working Group
Published:
Intended Status:
Informational
Expires:
Author:
D. Shuliak
SHULIAK CORP

Shuliak Isolation Protocol (SIP-1): Stateless Format-Preserving Pseudonymization and AST Quarantine for Local AI Agent Transports

Abstract

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.

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 19 May 2027.

▲

Table of Contents

1. Introduction and Problem Statement

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.

SIP-1 defines an inline, client-side cryptographic isolation boundary grounded in [NIST-FF1] and documented in the reference architecture [SIP1-ZENODO]. Sensitive tokens are bijectively mapped to format-valid synthetic twins in volatile memory before crossing tool or model boundaries.

2. Conventions and Terminology

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.

3. Deterministic AST Quarantine and FF1 Bijection

Before forwarding any JSON-RPC 2.0 request or tool output, a compliant SIP-1 interceptor MUST enforce two sequential local gates:

Implementations MUST NOT use the withdrawn FF3 or FF3-1 modes due to known small-domain cryptanalytic weaknesses.

4. Canonical Schema Lock and Attestation Envelope

To prevent post-approval tool definition tampering (Rug Pull attacks) and support tamper-evident compliance telemetry, tool schemas and audit records MUST be canonicalized using JSON Canonicalization Scheme (JCS) [RFC8785] prior to SHA-256 hashing and signed using Ed25519 [RFC8032].

{
  "sip_version": "1.0",
  "mode": "FF1-AES256-ZERO-EGRESS",
  "schema_jcs_sha256": "e3b0c44298fc1c149afbf4c8996fb924",
  "merkle_prev": "8f434346648f6b96df89dda901c5176b",
  "ed25519_sig": "base64url_detached_64byte_signature"
}

5. IANA Considerations

This document has no IANA actions.

6. Security Considerations

Ephemeral FF1 keys MUST 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 SHOULD be isolated so that cryptographic key destruction renders synthetic twins irreversible against dictionary enumeration while preserving outer hash-chain integrity.

7. References

7.1. Normative References

[NIST-FF1]
Dworkin, M., "Recommendation for Block Cipher Modes of Operation: Methods for Format-Preserving Encryption", NIST Special Publication 800-38G Revision 1, DOI 10.6028/NIST.SP.800-38Gr1, , <https://doi.org/10.6028/NIST.SP.800-38Gr1>.
[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
[RFC8032]
Josefsson, S. and I. Liusvaara, "Edwards-Curve Digital Signature Algorithm (EdDSA)", RFC 8032, DOI 10.17487/RFC8032, , <https://www.rfc-editor.org/info/rfc8032>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.
[RFC8785]
Rundgren, A., Jordan, B., and S. Erdtman, "JSON Canonicalization Scheme (JCS)", RFC 8785, DOI 10.17487/RFC8785, , <https://www.rfc-editor.org/info/rfc8785>.

7.2. Informative References

[SIP1-ZENODO]
Shuliak, D., "Shuliak Isolation Protocol (SIP-1): Stateless Checksum-Invariant Format-Preserving Pseudonymization and AST Sanitization for Autonomous AI Transports", DOI 10.5281/zenodo.24159380, , <https://doi.org/10.5281/zenodo.24159380>.

Author's Address

Dmitrii Shuliak
SHULIAK CORP
17 Pirosmani St.
6000 Batumi
Georgia