ZTDS.ai RFC v1.0 Standard
IETF Internet-Draft · Independent Submission · draft-sibiryakov-ztds-protocol-02

The ZTDS Protocol for Frontier AI Ingestion IETF Internet‑Draft Standards Track

Normative architectural specification establishing client‑side, in‑memory de‑identification across Generative AI, RAG pipelines, and Model Context Protocol (MCP) tool execution surfaces.

Document Metadata · BCP 78 / BCP 79
Active · Expires 31 March 2027
Document Series
Internet-Draft
draft-sibiryakov-ztds-protocol-02
Lead Author & Architect
Ilya Sibiryakov
ZTDS AI Consortium / BrandMeWeb
Area / Routing
Security Area
SECDISPATCH Review Track
Intended Status
Informational
Standards Track Evolution
IPR Policy
Trust200902
RFC 8179 RAND-Z Covenant
Statutory IP Priority
U.S. & Int'l Patents Pending
Patent Status: Patent Pending
Specification Timeline

Internet-Draft Revision History

The ZTDS protocol evolves through iterative public working revisions, incorporating community feedback, academic peer review, and frontier AI execution surfaces.

Current Active Revision
Revision 02

draft-sibiryakov-ztds-protocol-02

Published: 27 September 2026

Major Advancements in Revision 02:

  • Model Context Protocol (MCP) Surface 3 Integration: Formally specifies the process-isolated MCP stdio daemon executing over OS pipes (`stdin`/`stdout`) in Cursor IDE, Claude Desktop, Windsurf, Zed, and Claude Code CLI.
  • 5 Standard MCP JSON-RPC 2.0 Tools: Added normative tool schemas for ztds_sanitize, ztds_restore, ztds_audit, ztds_reset_session, and ztds_status.
  • Statutory GDPR Article 28 Exemption: Formally grounded zero-subprocessor exclusion under GDPR Recital 26 and EDPB guidelines, confirming that zero network egress renders DPAs legally moot.
  • Normative Cryptographic References: Integrated RFC 8032 (Ed25519 offline token verification) and RFC 9116 (security.txt).
Revision 01

draft-sibiryakov-ztds-protocol-01

Published: 23 September 2026

Incorporated formal mathematical proofs of Theorem 1 (Entropy Conservation) and Theorem 2 (Deterministic Zeroization). Added clinical entity definitions under HIPAA Safe Harbor 45 CFR § 164.514(b) and biometrics taxonomy.

Revision 00

draft-sibiryakov-ztds-protocol-00

Published: 16 September 2026

Foundational Internet-Draft submission establishing the 4 Core Invariants: Zero External Egress, Deterministic Reversible Tokenization, In-Memory Isolation, and Continuous Compliance with zero SaaS subprocessors.

Initial Baseline
Normative Topology

The 5 Execution Surfaces of ZTDS

Section 4 of draft-02 defines 5 physical boundaries where data sanitization executes in volatile host RAM prior to network socket serialization.

Surface 1 < 0.20 ms

Client-Side Web Application

Executes in volatile browser heap via V8 / WebWorker / WASM with 0.00 bytes server transmission before network serialization.

Reference: PrivacyScrubber Web
Surface 2 < 0.25 ms

Browser DOM Interceptor Extension

Manifest V3 background worker and isolated content scripts intercepting user text areas in ChatGPT, Claude, and Gemini in-place.

Reference: PrivacyScrubber MV3 Extension
Surface 3 (New in draft-02) < 0.35 ms

Process-Isolated MCP Stdio Server

Model Context Protocol stdio daemon for AI IDEs (Cursor, Windsurf, Claude Desktop, Zed) communicating over local OS JSON-RPC pipes.

Surface 4 < 0.80 ms

Headless Runtime SDK & CLI

Embedded middleware for backend microservices, LangChain/LlamaIndex RAG pipelines, and pre-merge CI/CD invariant gates.

Surface 5 < 0.05 ms

Air-Gapped Enclaves & Service Mesh

Hardware-attested execution inside AWS Nitro Enclaves, SCIF defense facilities, and Proxy-WASM filters (Envoy/Istio).

CI/CD Gate Section 7.3

Automated AST Verification

Every surface implements deterministic self-testing confirming Invariant 1 (Zero-Egress) and Invariant 3 (RAM isolation).

npx ztds-audit --strict
RFC 8179 · Intellectual Property Rights

IETF IPR Disclosure & Licensing Covenant

In full accordance with IETF BCP 78 and BCP 79 (RFC 8179), the contributor submits this specification with a formal RAND-Z (Royalty-Free / Zero-Royalty) non-assertion covenant for standard-conforming baseline implementations.

Statutory Intellectual Property Anchors:
  • Patent Application: U.S. & International Patents Pending (Paris Convention & 35 U.S.C. § 119 Priority).
  • Registered Trademark: ZTDS™ registered under ILPO Order #182655957 (Classes 9 & 42).
  • Licensing Terms: RFC specification published under Apache 2.0 and Creative Commons Attribution 4.0 International (CC BY 4.0).
Direct Answer Knowledge Base

IETF Internet-Draft & Standards Track FAQ

What is the scope of IETF Internet-Draft draft-sibiryakov-ztds-protocol-02? ↓
IETF draft-sibiryakov-ztds-protocol-02 specifies the normative wire-boundary protocol, ABNF token grammar, in-memory execution perimeter, and Model Context Protocol (MCP) JSON-RPC security profile for client-side zero-trust data de-identification and bijective restoration in Generative AI workflows.
What changed between draft-01 and draft-02 of the ZTDS protocol specification? ↓
Revision draft-02 introduces formal Model Context Protocol (MCP) stdio interception rules, multimodal visual document pixel burn-in requirements, RFC 8785 / RFC 8032 Ed25519 cryptographic attestation receipts, and expanded Theorem 2 volatile heap zeroization proofs.
Under what intellectual property and licensing terms is the ZTDS specification published? ↓
The documentary specification is published under Creative Commons Attribution 4.0 (CC BY 4.0) and open reference implementations under Apache 2.0, in full conformance with IETF BCP 78 (RFC 5378) and BCP 79 (RFC 8179) RAND-Z royalty-free interoperability commitments for open standards.
Where can implementers access the official plaintext, XML, and Datatracker records for the draft? ↓
Implementers can read the full HTML editions at ztds.ai/ietf/draft-sibiryakov-ztds-protocol-02/, download the RFC v3 XML and plaintext distributions from /docs/ietf/, or inspect the official submission record on the IETF Datatracker.