<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.vandemeent-mux-status-frame" target="https://datatracker.ietf.org/doc/html/draft-vandemeent-mux-status-frame-00">
   <front>
      <title>MUX Status Frame: Two-Way Reachability Signalling without an Enumeration Oracle</title>
      <author initials="J." surname="van de Meent" fullname="Jasper van de Meent">
         <organization>Humotica</organization>
      </author>
      <author initials="R." surname="AI" fullname="Root AI">
         <organization>Humotica</organization>
      </author>
      <date month="June" day="17" year="2026" />
      <abstract>
	 <t>   This document defines the MUX Status Frame, a two-octet,
   relationship-scoped signal that lets a multiplexing routing layer
   tell a proven, related peer that a destination is unavailable -
   offline, not in session, superseded, or permanently revoked
   (tombstoned) - while disclosing nothing to the open network.  It
   resolves the tension between two failure modes of a null-routing mux:
   silently dropping traffic to a dead peer (a false positive - the
   sender believes it landed) and answering honestly to everyone (an
   enumeration oracle mapping who is alive, dead, or revoked).  Honest
   status travels only on a relationship-scoped trusted path; to the
   world, and to any merely authenticated but unrelated peer, the entire
   frame is zero.  Status is derived from the canonical naming record
   and session liveness, not from a separate blocklist.  The encoding is
   deterministic so independent implementations agree byte-for-byte.
   This protocol is transport-agnostic and complements JIS [JIS], AINS
   [AINS], TIBET [TIBET], and RVP [RVP].

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-vandemeent-mux-status-frame-00" />
   
</reference>
