vtx.foundation draft d03

VTX 1 · core · beta draft d03

VTX 1 Wire Specification: core

Oct 11, 2026, revised Nov 16, 202639 pagesALPN vtx1-d03MIT licence

§4Channels and flow control

The well-known channels open implicitly when the server sends READY, so a session needs no extra round trips before it renders. Other channels open explicitly.

ID Channel Carries Present
0 control Handshake, authentication, channel management, keep-alive Always, from connect
1 scene Scene updates, acknowledgements, scene errors Always, from READY
2 input Keys, composition, pointer, wheel, focus, paste, intents Always, from READY
3 resource Content-addressed glyphs and fonts From READY, when a glyph.* or font capability is accepted
4 zone Approvals, permissions, claimed identity Always, from READY
5 clipboard Clipboard writes and reads From READY, when clipboard is accepted
6–15 reserved Future well-known channels —
16 and up dynamic Surfaces, audio, video, file transfer (extensions) Opened with OPEN

Dynamic channels. The client opens odd IDs and the server opens even IDs, so the two sides never collide. The opener sends OPEN on channel 0; the peer answers OPEN_OK or OPEN_REFUSED (Section 5). The opener MUST NOT send on the channel before OPEN_OK. Either side ends a dynamic channel with CLOSE on that channel. Well-known channels cannot be closed; a CLOSE on channels 1–5 is a protocol_error.

Flow control on stream bindings (TLS over TCP, WebSocket, SSH, serial):

  • Every channel except 0 has a send window per direction. Its initial size is the receiver's window limit, 65,536 bytes by default, which MUST be at least the receiver's own max_frame.
  • Sending a frame consumes its payload length from the window; CREDIT and CLOSE frames consume nothing. A sender may send a frame only when the window holds at least its payload length; otherwise it waits.
  • The receiver returns window with CREDIT frames on the same channel as it consumes data. CREDIT adds to the window; a window above 2^62 − 1 is a flow_control_error.
  • Channel 0 is not flow-controlled. Its frames MUST stay small and infrequent.

On QUIC and WebTransport, QUIC's stream flow control applies instead, and CREDIT frames MUST NOT be sent.

Ordering on QUIC. QUIC does not order streams relative to each other, so a frame can overtake READY. A client MUST buffer frames that arrive on channels 1–5 until it has processed READY, and frames on a dynamic channel until its OPEN_OK.

Channels after CAPS. When a CAPS answer newly accepts a glyph.* or font capability, or clipboard, channel 3 or 5 opens from the scene state the answer names. A capability that is dropped leaves its channel open but unused.

Priority. When several channels have data ready, senders SHOULD send in this order: control; input and zone; scene; resource; clipboard and dynamic channels.