<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rfc [
  <!ENTITY nbsp "&#160;">
  <!ENTITY zwsp "&#8203;">
  <!ENTITY nbhy "&#8209;">
  <!ENTITY wj "&#8288;">
]>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="info" docName="draft-sakai-hcttp-00" ipr="trust200902" obsoletes="" updates="" submissionType="independent" xml:lang="en" version="3">
  <front>
    <title abbrev="HCTTP">Human Conversational Turn-Taking Protocol (HCTTP)</title>
    <seriesInfo name="Internet-Draft" value="draft-sakai-hcttp-00"/>
    <author fullname="Hideaki Sakai" initials="H." surname="Sakai">
      <organization>Crestboz Corporation</organization>
      <address>
        <postal>
          <country>Japan</country>
        </postal>
        <email>hideaki.sakai@crestboz.co.jp</email>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <area>General</area>
    <workgroup>Network Working Group</workgroup>
    <keyword>Conversation Analysis</keyword>
    <keyword>Turn-Taking</keyword>
    <keyword>April Fools</keyword>
    <keyword>Protocol</keyword>
    <keyword>RFC6919</keyword>
    <abstract>
      <t>This document specifies the Human Conversational Turn-Taking Protocol (HCTTP), an integrated session-layer communication protocol for multi-node human spoken interaction. HCTTP formalizes connection establishment (Three-Way Handshake), token arbitration, turn transitions, real-time backchannel signaling (ACK/NACK), dynamic rate adaptation, conversational padding (filler frames), collision recovery, and standardized conversational status codes over shared acoustic channels.</t>
    </abstract>
  </front>
  <middle>
    <section anchor="intro" numbered="true" toc="default">
      <name>Introduction</name>
      <t>Human spoken dialogue over shared verbal and acoustic channels frequently suffers from coordination anomalies, including premature interruption, unhandled transmission silence, buffer starvation, context mismatch, and packet collisions (overlapped speech). While sociological Conversation Analysis (CA) has observed empirical turn-taking mechanics, practical dialogue systems and human participants often lack a formal, enforceable protocol specification.</t>
      <t>This memo standardizes the Human Conversational Turn-Taking Protocol (HCTTP), bridging empirical Conversation Analysis models with rigorous network transport specifications.</t>
    </section>
    <section anchor="conventions" numbered="true" toc="default">
      <name>Conventions and Terminology</name>
      <t>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 <xref target="RFC2119"/> <xref target="RFC8174"/>.</t>
      <t>Additionally, in recognition of habitual human communication failure modes, key words from <xref target="RFC6919"/> are incorporated: "MUST (BUT WE KNOW YOU WON'T)", "SHOULD CONSIDER", and "OUGHT TO".</t>
    </section>
    <section anchor="session-mgmt" numbered="true" toc="default">
      <name>Session Management and Handshake</name>
      <section anchor="handshake" numbered="true" toc="default">
        <name>Three-Way Handshake (Session Establishment)</name>
        <t>Prior to transmitting conversational payload, nodes MUST establish a stateful session via a standard Three-Way Handshake:</t>
        <artwork name="" type="" align="left" alt=""><![CDATA[
Initiator (Node A)                        Responder (Node B)
       |                                          |
       |-------- SYN ("Got a second?").---------->|
       |                                          |
       |<------- SYN-ACK ("Sure, what's up?") ----|
       |                                          |
       |-------- ACK ("Great, so...") ----------->|
       |                                          |
       | [Session Established: Payload Streaming] |
]]></artwork>
      </section>
      <section anchor="teardown" numbered="true" toc="default">
        <name>Graceful Teardown and Reset</name>
        <t>To terminate a conversational session gracefully, the initiating node MUST transmit a FIN frame (e.g., "Anyway, I'll let you get back to it"). The session is formally closed upon receipt of a FIN-ACK (e.g., "Sounds good, talk soon").</t>
        <t>In the event of unexpected physical interrupts (e.g., incoming phone call, urgent alarm), an immediate RST flag (e.g., "Gotta run!") MAY be broadcast to tear down the connection unilaterally.</t>
      </section>
    </section>
    <section anchor="architecture" numbered="true" toc="default">
      <name>Architecture and Frame Formats</name>
      <section anchor="tcu" numbered="true" toc="default">
        <name>Turn Constructional Unit (TCU)</name>
        <t>The primary atomic data packet emitted by a transmitting speaker node is defined as a Turn Constructional Unit (TCU):</t>
        <artwork name="" type="" align="left" alt=""><![CDATA[
+-------------------------------------------------------------------+
|  Payload (Linguistic Data)  |  TRP Header (Acoustic / Syntactic)  |
+-------------------------------------------------------------------+
]]></artwork>
        <ul spacing="normal">
          <li><strong>Payload:</strong> Semantic and verbal content (words, phrases, sentences).</li>
          <li><strong>TRP Header (Transition Relevance Place):</strong> An end-of-frame marker denoted by intonational pitch-downs, syntactic completion points, or respiratory pauses indicating readiness to yield the token (EOF).</li>
        </ul>
      </section>
      <section anchor="feedback-frames" numbered="true" toc="default">
        <name>Feedback Frame (Backchannel Signals)</name>
        <t>A listening node MAY transmit asynchronous control frames over an out-of-band backchannel without interrupting the primary TCU stream:</t>
        <artwork name="" type="" align="left" alt=""><![CDATA[
+----------------------------------------------------------------+
|  Frame Type (ACK / NACK / WAIT)  |  Bitrate / Pitch Modulator  |
+----------------------------------------------------------------+
]]></artwork>
        <ul spacing="normal">
          <li><strong>ACK (Standard Acknowledge):</strong> e.g., "Yeah", "Uh-huh", "Right". Confirms successful packet decoding and authorizes current transmission bitrate.</li>
          <li><strong>DUP_ACK (Duplicate ACK / Fast-Forward):</strong> e.g., "Yeah-yeah-yeah", "Right-right". Signals payload pre-processing and requests immediate payload compression towards terminal conclusions.</li>
          <li><strong>NACK (Negative Acknowledge):</strong> e.g., "Huh?", "What?", head-tilt modulation. Signals decode failure or context misalignment, demanding retransmission with alternate linguistic encoding.</li>
          <li><strong>EMOTIONAL_ACK (QoS Amplifier):</strong> e.g., "No way!", "Seriously!?". Signals high engagement and amplifies conversational bandwidth.</li>
        </ul>
      </section>
      <section anchor="filler-padding" numbered="true" toc="default">
        <name>Filler Frames (TOKEN_HOLD Padding / NOP)</name>
        <t>When a transmitting node requires computational latency for lexical retrieval without relinquishing the speaking token, it MAY transmit zero-entropy conversational padding frames (TOKEN_HOLD), commonly realized as "Um...", "Uh...", or "Like...".</t>
        <t>Nodes MUST NOT (BUT WE KNOW YOU WILL) emit continuous TOKEN_HOLD padding exceeding 3.0 seconds. Exceeding this threshold triggers an automatic 408 (Request Timeout) on peer listening nodes.</t>
      </section>
    </section>
    <section anchor="algorithm" numbered="true" toc="default">
      <name>Turn-Taking Algorithm</name>
      <t>Upon detection of a TRP delimiter in an incoming TCU, all participating nodes MUST execute arbitration according to the following deterministic precedence rules:</t>
      <artwork name="" type="" align="left" alt=""><![CDATA[
[Transmitting Node: TRP Detected]
       |
       +---> (Rule 1) Explicit Next-Speaker Routing?
       |              |-- YES: Token transferred to designated node.
       |              +-- NO : Proceed to Rule 2.
       |
       +---> (Rule 2) Self-Selection Contention (CSMA/CD)
       |              |-- First node sensing carrier gains Token.
       |              +-- No transmission initiated: Proceed to Rule 3.
       |
       +---> (Rule 3) Speaker Continuation
                      |-- Transmitting node retains Token for next TCU.
]]></artwork>
      <ul spacing="normal">
        <li><strong>Rule 1 (Explicit Routing):</strong> Target address explicitly designated via vocal addressing (name) or directional beamforming (gaze).</li>
        <li><strong>Rule 2 (CSMA/CD Contention):</strong> Receiving nodes contend for the acoustic medium on a first-come, first-served basis.</li>
        <li><strong>Rule 3 (Speaker Continuation):</strong> Transmitting node retains the session and initiates subsequent TCU transmission.</li>
      </ul>
      <t>Receiving nodes MUST (BUT WE KNOW YOU WON'T) refrain from executing Rule 2 contention prior to explicit TRP delimiter verification.</t>
    </section>
    <section anchor="flow-control" numbered="true" toc="default">
      <name>Flow Control and Rate Adaptation</name>
      <t>Transmitting nodes MUST dynamically adapt payload delivery based on feedback frames:</t>
      <ul spacing="normal">
        <li><strong>ACK Received:</strong> Maintain bitrate; continue current TCU stream.</li>
        <li><strong>DUP_ACK Received:</strong> Transmitting node SHOULD CONSIDER compressing payload and advancing directly to the conclusion.</li>
        <li><strong>NACK Received:</strong> Halt stream; retransmit previous TCU at a lower baud rate with simplified semantic constructs.</li>
        <li><strong>NO_ACK Timeout:</strong> If no ACK is received within 2.0 seconds, enter Keep-Alive state by pausing transmission and issuing a PING ("Are you still there?"). Resume upon receipt of PONG ("Sorry, yeah, listening").</li>
      </ul>
    </section>
    <section anchor="collision" numbered="true" toc="default">
      <name>Collision Detection and Recovery</name>
      <t>When multiple nodes emit sound carriers simultaneously, a channel collision (Overlapped Speech) occurs:</t>
      <artwork name="" type="" align="left" alt=""><![CDATA[
Node A: ---[ TCU Payload A ]-------------------------->
Node B:           |---[ TCU Payload B ]---> (COLLISION!)
                  ^
           Collision Detected
]]></artwork>
      <t>Upon collision detection:</t>
      <ol spacing="normal">
        <li>The invading or lower-priority node MUST immediately execute PAUSE and revert to the listening state.</li>
        <li>The yielding node SHOULD emit an ACK_REPAIR frame (e.g., "Sorry, go ahead").</li>
        <li>Channel arbitration resets to standard Rule 1/2 state.</li>
      </ol>
    </section>
    <section anchor="status-codes" numbered="true" toc="default">
      <name>Conversational Status Codes</name>
      <t>HCTTP adopts standard three-digit status codes to represent session feedback and cognitive states:</t>
      <table anchor="status-table" align="center">
        <name>HCTTP Conversational Status Codes</name>
        <thead>
          <tr>
            <th align="left">Code</th>
            <th align="left">Name</th>
            <th align="left">Description</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">100</td>
            <td align="left">Continue</td>
            <td align="left">Listener acknowledges receipt and authorizes continued narration.</td>
          </tr>
          <tr>
            <td align="left">200</td>
            <td align="left">OK</td>
            <td align="left">Linguistic payload fully decoded and accepted.</td>
          </tr>
          <tr>
            <td align="left">400</td>
            <td align="left">Bad Context</td>
            <td align="left">Utterance violates conversational context or logical cohesion.</td>
          </tr>
          <tr>
            <td align="left">403</td>
            <td align="left">Forbidden Topic</td>
            <td align="left">Topic violates social boundaries or taboo constraints.</td>
          </tr>
          <tr>
            <td align="left">408</td>
            <td align="left">Request Timeout</td>
            <td align="left">Speaker or listener stalled in prolonged silence (> 3.0s).</td>
          </tr>
          <tr>
            <td align="left">429</td>
            <td align="left">Too Many Words</td>
            <td align="left">Speaker exceeds listener buffer capacity (machine-gun talk).</td>
          </tr>
          <tr>
            <td align="left">503</td>
            <td align="left">Service Unavailable</td>
            <td align="left">Node cognitive processing exhausted (fatigue or intoxication).</td>
          </tr>
        </tbody>
      </table>
    </section>
    <section anchor="faults" numbered="true" toc="default">
      <name>Fault Definitions and Protocol Errors</name>
      <table anchor="fault-table" align="center">
        <name>Protocol Fault Codes</name>
        <thead>
          <tr>
            <th align="left">Fault Code</th>
            <th align="left">Role</th>
            <th align="left">Description and System Impact</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">UDP Mode</td>
            <td align="left">Transmitter</td>
            <td align="left">Omits TRP headers and ignores ACK frames. Causes listener buffer overflow.</td>
          </tr>
          <tr>
            <td align="left">NACK Invalidation</td>
            <td align="left">Transmitter</td>
            <td align="left">Ignores NACK frames; fails to retransmit, causing session corruption.</td>
          </tr>
          <tr>
            <td align="left">ACK Storm</td>
            <td align="left">Receiver</td>
            <td align="left">Emits rapid ACK frames without decoding. Results in semantic divergence.</td>
          </tr>
          <tr>
            <td align="left">Silent Drop</td>
            <td align="left">Receiver</td>
            <td align="left">Omits ACK during deep internal processing, inducing unnecessary PINGs.</td>
          </tr>
          <tr>
            <td align="left">Interrupt Bug</td>
            <td align="left">Receiver</td>
            <td align="left">Forces Rule 2 before TRP detection, inducing excessive collisions.</td>
          </tr>
        </tbody>
      </table>
    </section>
    <section anchor="iana" numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>This document requests that IANA assign a well-known port number for conversational token mediation under the Service Name and Transport Protocol Port Number Registry:</t>
      <artwork name="" type="" align="left" alt=""><![CDATA[
Service Name:       hcttp
Transport Protocol: tcp
Port Number:        7110
Description:        Human Conversational Turn-Taking Protocol
Assignee:           IESG <iesg@ietf.org>
Contact:            Conversation Analysis Working Group
]]></artwork>
      <t>Additionally, IANA is requested to establish a registry for HCTTP Conversational Status Codes as defined in Section 7.</t>
    </section>
    <section anchor="security" numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>Nodes MUST implement appropriate authentication and emotional encryption (Politeness Protocol Layer) to prevent unauthorized channel intrusion, malicious payload injection, or Denial-of-Service (DoS) via excessive filibustering or interruptions.</t>
    </section>
    <section anchor="contributors" numbered="false" toc="default">
      <name>Contributors</name>
      <t>The following non-human entity contributed significantly to the protocol specification, state machine formalization, and drafting of this document:</t>
      <ul spacing="normal">
        <li><strong>Gemini</strong> (Google)</li>
      </ul>
    </section>
    <section anchor="acknowledgments" numbered="false" toc="default">
      <name>Acknowledgments</name>
      <t>The author would like to thank Gemini (Google) for collaborative protocol design and drafting, as well as the Conversation Analysis research community for empirically reverse-engineering human turn-taking state machines.</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 fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
        </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 fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
        </reference>
      </references>
      <references>
        <name>Informative References</name>
        <reference anchor="RFC6919" target="https://www.rfc-editor.org/info/rfc6919">
          <front>
            <title>Further Key Words for Use in RFCs to Indicate Requirement Levels</title>
            <author fullname="R. Barnes" initials="R." surname="Barnes"/>
            <author fullname="S. Kent" initials="S." surname="Kent"/>
            <author fullname="E. Rescorla" initials="E." surname="Rescorla"/>
            <date month="April" year="2013"/>
          </front>
          <seriesInfo name="RFC" value="6919"/>
        </reference>
      </references>
    </references>
  </back>
</rfc>