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

§2Transport bindings

VTX needs an encrypted, reliable, ordered byte stream. On QUIC-based transports each channel also gets its own stream, which removes head-of-line blocking between channels. Every binding carries the same frames (Section 3).

Binding Carrier Security Channel mapping
QUIC QUIC v1 (RFC 9000), ALPN vtxq1 TLS 1.3 (RFC 9001) Channel 0 on client-initiated bidirectional stream 0; every other channel on one unidirectional stream per direction
WebTransport WebTransport over HTTP/3; URI path selects the application TLS 1.3 As QUIC, using WebTransport streams
TLS over TCP TCP, ALPN vtx1 TLS 1.3 All channels multiplexed on one byte stream
WebSocket RFC 6455 over HTTPS, subprotocol vtx1 TLS 1.3 As TLS over TCP; each binary message holds one or more whole frames
SSH SSH subsystem vtx@vtx.foundation SSH transport and user authentication As TLS over TCP
Serial PPP over UART, USB CDC, radio links or pipes TLS 1.3, as TLS over TCP; Noise in the experimental bare-metal profile As TLS over TCP (below)

Rules for all bindings

  • Every binding MUST encrypt the connection and authenticate the server. TLS-based bindings MUST use TLS 1.3 or later and refuse earlier versions. There is no unencrypted VTX.
  • HELLO MUST NOT be sent as TLS early data (0-RTT), because early data can be replayed.
  • On QUIC and WebTransport, a sender opens a channel's unidirectional stream when it first sends on that channel. All frames on one stream MUST carry the same channel ID.
  • QUIC DATAGRAM frames (RFC 9221) are used only by extensions: live media (Media 1), forwarded UDP (Exec 1), viewer presence (Viewers 1), and gamepad state and sensor readings (Sensors 1).
  • Browsers cannot query SVCB records, so for browser clients vtx://host[:port]/app maps to https://host[:port]/.well-known/vtx/app for WebTransport, and to wss:// at the same path for WebSocket. Browser clients use WebTransport where available and WebSocket otherwise.
  • Over SSH, the SSH user is the VTX user: the server offers auth method ssh (Section 5). The subsystem name carries the @vtx.foundation suffix until IETF registration permits plain vtx (RFC 4250 §4.6.1).

Browser clients and origins. A server that accepts WebSocket or WebTransport connections MUST check the Origin header against an allowlist, and MUST refuse unauthenticated, token and tls-cert sessions from any origin outside it, so that a web page cannot drive a VTX server through a visitor's browser. The trusted zone's guarantees hold only when the server does not supply the client code (Section 12), so the reference web client is served from an origin run independently of any VTX server.

QUIC streams. Each endpoint MUST allow its peer at least 16 unidirectional streams and 1 bidirectional stream. RESET_STREAM or STOP_SENDING on the stream of channel 0–5 is a connection error protocol_error; on a dynamic channel it closes that channel.

Serial binding. In v1, a serial link carries PPP (RFC 1661, with RFC 1662 framing), and VTX runs over it with the TLS over TCP binding. Serial clients therefore get the same encryption and server authentication as any other. A bare-metal profile for devices without an IP stack (COBS-framed link packets with a CRC-32C, an ARQ layer, then Noise) stays experimental until the beta names one ARQ implementation, and is not required for conformance.

Noise. Where Noise is used, the pattern is Noise_XX_25519_ChaChaPoly_BLAKE2s, or Noise_IK_25519_ChaChaPoly_BLAKE2s when the client has the server's static key pinned. The prologue is the ASCII Noise token (vtx1-d03 in this draft), and each Noise message is preceded by its length as a 2-byte big-endian integer. With XX, the client pins the server key on first use and refuses a changed key unless the user accepts it in the trusted zone. Noise proves a key, not a host name: the zone shows the key fingerprint as the server's identity, and the webauthn, oidc and x509 sign-in methods, which all bind to a host name, are unavailable unless provisioning bound the key to one.