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

§16Identifiers and registries

ScaiLabs maintains these registries during the beta. They move to the foundation or consortium when it forms. The specification and reference implementation are MIT-licensed.

Identifiers

Identifier Value Status
URI scheme vtx Provisional registration to request (RFC 7595)
TLS ALPN vtx1 (TLS over TCP), vtxq1 (QUIC); in draft d03 vtx1-d03, vtxq1-d03 To request from IANA at freeze
SVCB service _vtx, with Port Prefix Naming Scheme mapping in Section 5; _vtx to enter the underscored node names registry (RFC 8552)
SRV services _vtx._udp, _vtx._tcp To request from IANA
Default port (UDP and TCP) 22100 (0x5654, "VT" in ASCII), requested Requested from IANA; beta implementations use it from draft d01 and move if IANA assigns another number. Deployments SHOULD still publish SVCB or SRV records, which take precedence
WebSocket subprotocol vtx1; in draft d03 vtx1-d03 To request from IANA at freeze
WebSocket subprotocol, application interface vtx-app1; in draft d03 vtx-app1-d03 To request from IANA at freeze
SSH subsystem vtx@vtx.foundation; in draft d03 vtx-d03@vtx.foundation Private name, valid without registration
Noise prologue vtx1; in draft d03 vtx1-d03 Defined here
Media type (text form) application/vnd.vtx.jsonl Vendor tree, at freeze: +jsonl is not a registered suffix, and the standards tree needs a standards body
Core catalog tag:vtx.foundation,2026:vtx/catalog/core/1 Tag URI, needs no registration
Well-known URI suffix vtx, for browser clients (Section 2) To register (RFC 8615)

Draft identifiers. Until the specification freezes, implementations use the draft-numbered identifiers, so two drafts never talk to each other by accident. This is draft d03. The labels inside hashes, such as vtx1-approval and vtx1-oidc, stay the same across drafts. Draft d02 moved the domain-scoped names, the SSH subsystem and the tag URIs of catalogs and schemas, from scailabs.ai to vtx.foundation.

Registries and their rules

Registry Ranges Rule
Frame types 0x00–0x0F common; 0x10–0x3F per channel, defined here or by the extension that defines the channel type; the extensions assign 0x22 WAIT on channel 0 (Viewers 1), 0x14 FETCH and 0x15 GONE on channel 5 (Transfer 1), 0x1F WINDOW on channel 2 (Windows 1) and 0x23 LAYOUT on channel 0 (Displays 1); 0x40–0x3FFF future versions; 0x4000 and up experimental Experimental types MUST be gated by an extension capability
Well-known channels 0–5 assigned; 6–15 reserved Assigned by specification only
Capability keys Unqualified names for this spec; name@domain for extensions Section 5 lists the core's keys; the extensions' keys are in ext/registry.json
Close codes 0x00–0x0D assigned by the core; 0x0E–0x11 assigned by extensions; 0x12–0x3F reserved; 0x40 and up implementation-defined Section 14
Scene error codes Strings listed in Section 7 New codes by specification
Component catalogs Tag or other URIs Anyone may publish one; clients advertise what they render
Permissions Strings listed in Section 12, with those the extensions add New permissions by specification
Input device classes, gestures, accessibility actions Lists in Section 11; name@domain for extension classes New entries by specification; extensions need no registration
Auth methods Strings listed in Section 5; the extensions add rpk, device and enrol (Devices 1) and ticket (Brokering 1) New methods by specification; name@domain for extensions
AUTH_FAILED reasons credential, expired, revoked, unsupported, locked; the extensions add denied (Devices 1) and ticket (Brokering 1) New reasons by specification
Resource kinds Strings listed in Section 10; the extensions add image, theme, catalog, audio and video kinds New kinds by specification
Haptic effects Strings listed in Section 11 New effects by specification; name@domain for extensions
Colour roles fg, bg, muted, accent, info, success, warning, critical By specification only, since every client must map them
Dynamic channel types Strings listed in Section 4; the extensions add audio and video (Media 1), transfer (Transfer 1), exec, forward and listen (Exec 1), device (Devices 1), viewers (Viewers 1), sensor (Sensors 1), broker (Brokering 1), drive (Drives 1), print (Printers 1), mediadev (Media Devices 1), smartcard (Smart Cards 1), usb (USB 1) and wasm (WASM 1) New types by specification; name@domain for extensions
Pointer shapes CSS cursor keywords listed in vtx-ops-1.schema.json New shapes by specification
Application interface kinds Strings listed in Section 17, with those the extensions add New kinds by specification

Every value the extensions assign in these registries is listed in ext/registry.json of the definitions bundle, which tools/validate.py checks against the CDDL on every run.