Internet-Draft M. Davis Intended status: Informational Shared Health Services Expires: September 17, 2026 March 17, 2026 Tyndale: Semantic Addressing Protocol (Translation Yare Native Distributed Addressing Language Engine) draft-davis-tyndale-00 Abstract Notation Conventions ASCII notation is normative. Unicode notation is informative. Both encodings produce identical semantic output. The choice of representation does not alter meaning -- it demonstrates the protocol's encoding independence. This is not a modern innovation. The protocol formalizes patterns that have emerged independently across human communication systems for 60,000 years: Aboriginal songlines, medical notation (Rx), ham radio Q-codes (QTH), maritime signals (SOS), and internet shorthand (1337, TL;DR). This document specifies Tyndale, an application-layer semantic addressing protocol. Where traditional compression transmits reduced content (M -> C -> M), Tyndale transmits coordinates that the receiver expands locally (M -> A, Σ(A) -> M'). The receiver's substrate already contains the meaning; transmission provides location, not payload. The selection formula tau = (M / S) x R x G optimizes for meaning preserved per signal spent (M/S), resilience across expression systems (R), and cognitive alignment with receiver processing (G). Bandwidth-constrained environments -- disaster response networks, degraded infrastructure, deep space communications -- require semantic transmission under conditions where traditional compression fails. When every bit costs power, time, or lives, communication systems need a different primitive. Taft's teletype (1909). Voyager 1 (160 bps @ 15 billion miles). iPhone. Same protocol. Tyndale is to natural language what DNS is to IP addresses. The mathematics describes how meaning moves. 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 August 31, 2026. 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. 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. Table of Contents 0. Vega (Preface) 1. ORG 100h (Introduction) 1.1. Soup Sandwich (Problem Statement) 1.2. Signal Injection (Research Contribution) 1.3. Macro (Formal Distinction) 1.4. Jump Coordinates (Document Organization) 2. git log (Prior Work) 2.1. MacGyver's Paperclip (Engineering Precedent) 2.2. NASA->1_SHOT_CHAR_COMMAND->VOY_I 2.3. Hx BIT_GRID (Historical Addressing Systems) 2.4. Babel.obj (Linguistic Formalization) 3. IF/THEN (Approach) 3.1. Protocol Flow 3.2. Notation System 3.3. Library Taxonomy 3.4. Domain Addressing 3.5. Addressor (Sender) 3.5.0. LAYER 0: θ Rotation (Context Manager) 3.5.1. LAYER 1: Conditional Logic 3.5.2. LAYER 2: Substrate Measurement 3.5.3. LAYER 3: Phase Optimization 3.5.4. LAYER 4: τ Optimization 3.5.5. LAYER 5: Address Generation 3.6. Addressee (Receiver) 4. ping -c 15e9 4.1. -s (Constraint) 4.2. -i (Baseline) 4.3. -W (Round-trip) 4.4. -q (Comparison) 4.5. -t (Compatibility) 4.6. -v (Examples) 4.7. SCOTTY (The Engineering Reality) 4.8. diff -r (Domain Coverage Validation) 5. TODO (Future Work) 5.0. Infrastructure, Not Application 5.0.1. The Empty Summer 5.1. Content Delivery Networks 5.2. Web Infrastructure 5.3. Decentralized Mesh Networks 5.4. Economic Access and Cross-Language Communication 5.5. Accessibility and Non-Literate Expansion 5.6. Space Mission Optimization 6. chmod 000 (Security) 6.1. Trust Model 6.2. Transport Security 6.3. Receiver-Controlled Expansion 6.3.1. The Expansion Constraint 6.4. Library Integrity 6.5. Denial of Service 6.6. Replay Considerations 6.7. Semantic Navigation Space 6.8. Privacy Considerations 6.9. Cross-Platform Variance 6.10. Residual Risk 7. IANA Considerations 7.1. Rationale for Non-Registration 8. INT 21h, AH=4Ch (Conclusion) 9. References 9.1. Normative References 9.2. Informative References Acknowledgments Author's Address 0. Vega (Preface) March 2026. Wilmington, DE. Mercurial. Century-old stone archives meet floor-to-ceiling glass innovation hubs along the Brandywine. Morning light declares industrial tradition. Spring emerges amid the thaw. It is now difficult to recall the partition. The early twenty-first century. Human communications moved through systems optimized for data transmission on pipes built for packets. A digital frontier routing bits with extraordinary precision. Vast networks compressing for speed, mapping coordinates, standardizing characters, and synchronizing every clock. Bandwidth at infrastructure scale. Engineers went about their work - building, testing, deploying. TCP moved data. DNS resolved names. HTTP served content. Transmitted data flowing through pipes for 57 years. Constantly optimized and refined. Yet beneath the packet layer, an older logic was running. A pattern running for 60,000 years like the rhythmic pulse of a drum. It regarded the digital pipes waiting for formalization. The shift came quietly. In the twenty-sixth year, a formalization. 1. ORG 100h (Introduction) Human communication systems have independently developed semantic addressing patterns across cultures and domains for millennia. Let's walk through some examples: A grandmother walks a child through the desert, singing. No maps. No writing. The song IS the signal — 60,000 years of navigation encoded in melody because memory was all they had. A Japanese radio operator needs to reach an American ship. Static. Language barrier. Three letters — QTH — and both know: "location?" The code IS the signal. A nurse has seconds. A doctor's handwriting is terrible. Rx. Dx. Tx. Lives depend on density. The abbreviation IS the signal. A teenager has 140 characters to reach the whole world. No shared language. TARGET (🎯), HEART (❤️), FIRE (🔥) — and everyone understands. The emoji IS the signal. See the pattern? Different millennia. Different constraints. Same architecture: encode meaning as coordinates, transmit the address, receiver expands locally. Signal encodes. Coordinates transmit. Receiver expands. SENDER SHARED RECEIVER | | | meaning -----> [address] -----> substrate expands | | | converts library recognizes to signal lookup locally Here's how this actually works: the sender doesn't transmit content. The sender transmits coordinates saying "hey, look at position X in your library." The receiver? Already has the meaning stored locally in their substrate (shared context with the sender). The receiver just looks up the coordinates. This works because the meaning is already there. The library lives in both places. The substrate already contains the constellation. The signal just says where to look. That's why Tyndale crosses languages. You're not translating words. You're pointing at locations. The receiver expands in their native tongue because their substrate already has that address mapped. Tyndale formalizes the architecture these systems share. 1.1. Soup Sandwich (Problem Statement) So here's the problem: How does meaning survive the journey? Compression says: make it smaller, expand it back. But compression transmits content — and content degrades. Translation says: map these words to those words. But translation requires word-to-word equivalence — and some meanings have no equivalent. There is no English word for طرب. You cannot translate it. You can only point at where it lives. Current approaches face fundamental limitations: o Translation systems require word-to-word or phrase-to-phrase mapping, losing cultural and contextual nuance o Bandwidth-constrained environments (emergency communications, low-infrastructure regions, deep space) cannot support verbose transmission o No standardized addressing system exists for semantic content comparable to DNS for network locations This protocol is explicitly designed for environments in which literacy, power, bandwidth, trust, and infrastructure cannot be assumed. Tyndale takes a different path: the meaning is already at the destination. The receiver's substrate contains the constellation. Don't transmit content. Transmit coordinates. 1.2. Signal Injection (Research Contribution) So what does Tyndale do? o Universal Applicability: Deploys on existing infrastructure without modification o Protocol Specification: Application-layer addressing system mapping to OSI model o Reliability Architecture: tau (τ) measures survival probability — not compression ratio. The question isn't "how small? It's "How likely is it the meaning arrives intact? o Pattern Recognition: Single-source transmission fails the same way across every domain. The evidence spans decades: 1962 Mariner 1 Missing hyphen destroys rocket 1983 Gimli Glider Metric/imperial nearly crashes jet 1990 Hubble Measurement error blurs mirror for yrs 1999 Mars Climate Unit mismatch craters $328M spacecraft 2005 Mizuho Securities Swapped numbers costs $225M 2007 Alitalia Missing letter costs $503,000 2009 Waterford Crystal Extra letter kills 124-year company 2012 JPMorgan Excel formula error loses $6 billion See it? Five decades. Same pattern. Math. Code. Spelling. Physics. Data entry. The domain doesn't matter. Tyndale is reliability engineering. R > 1 means meaning survives. 1.3. Macro (Formal Distinction) Alright, so lets look at the difference between traditional compression and Tyndale. Traditional Compression: M -> C -> M (meaning -> compressed -> meaning via decompression function) Tyndale Addressing: M -> A, then Σ(A) -> M' (meaning -> address, receiver's substrate S expands locally) ENCODING COMPARISON: Model ASCII Unicode ---------- ---------------- ------------- Traditional M -> C -> M M → C → M Tyndale M -> A, Sigma(A)->M' M → A, Σ(A)→M̂ No decompression function transmission required. The receiver performs expansion using a local semantic map. TCP moves DATA. Tyndale moves COORDINATES. This is axiomatic. Define 0. Define successor S (S means "next"). 1 = S(0). 2 = S(S(0)). Base case: n + 0 = n Recursive step: n + S(m) = S(n + m) Therefore: S(0) + S(0) = S(S(0) + 0) = S(S(0)) = 2. Q.E.D. Whitehead and Russell needed 379 pages to reach that proof. Zero unproven assumptions. "What is a set?" to "Therefore, 1+1=2." Tyndale builds from one rule: M -> A, Σ(A) -> M'. Meaning converts to address. Receiver expands locally. Everything that follows derives from this. 1.4. Jump Coordinates (Document Organization) There is nothing unfamiliar in what follows. The patterns are already present—in your professional vocabulary, in the addressing systems you use daily without naming, in your substrate. This document formalizes patterns the reader already uses: git log has been transmitting for 60,000 years (§2), IF/THEN specifies the protocol (§3), ping -c 15e9 validates the claims (§4), TODO points forward (§5), chmod 000 (§6), IANA (§7), INT 21h (§8). For the sections that follow, the formalization is the only variable. The patterns are eternal. 2. git log (Prior Work) Submitted for your approval: a protocol that builds on a pattern the universe has exhibited for 13.8 billion years. Deployed semantic addressing systems that have been running for decades, centuries, since... ? In version control, 'git log' shows commit history—who changed what, when, and why. Patterns emerge. Different contributors, same architecture. Three independent paths converged on the same structure. Engineers building systems. Physicists measuring state. Humans addressing meaning under constraint. No coordination. Same problem. Same solution. Different implementations. When constraints force efficiency, structure appears. Engineers faced legacy translation. Physicists faced state transformation. Humans faced bandwidth limits sixty thousand years ago and never stopped. The signal was always there. Engineers found it in transpilers. Physicists found it in structured states. Humans found it in songlines. This section documents the convergence. 2.1. MacGyver's Paperclip (Engineering Precedent) "A paper clip can be a wondrous thing." In 1912, maritime radio operators faced a hard constraint. Ships at sea. Different languages. Morse code charged by the letter. Static, noise, time. Lives at stake. A solution emerged at the Second International Radiotelegraph Convention: Q-codes. 45 three-letter signals replacing entire sentences. QTH? -> "What is your location?" QSL -> "I confirm receipt." 73 -> "Best regards" Why Q? Pragmatics. Few words in any language start with 'Q'. Add '?' it becomes a query. Without? A statement. Universal fixed meaning. Still operational. Deployed July 1, 1913. Different ships. Different languages. Same destination. --- The pattern held. Amateur radio operators adopted the same architecture. Bandwidth limits. Signal fading. Cross-lingual reach. CQ -> "Calling all stations" QTH -> "My location is..." 73 -> "Best regards" The solution spread. Deployed, formally, Oct 1934. --- ASCII emerged as transformation hub. Seven bits serving as shared coordinat