You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
id: design: id broker / serve-proxy role (from #5671) #5792
Follow-on design ticket from #5671 — its decomposition sketch names this as a separate design, and the parent's acceptance requires these tickets to be filed and linked. Filed in the 2026-11-04 gap pass (WS-F) so the design work exists and can be prioritised on its own merits; implementation timing is a separate decision, possibly months out.
What this design must settle
The broker role's protocol: framing over TCP/HTTP(S), multiplexing, keepalive and resumption — the shape of the in-id relay that UDP-denied clients fall back to.
Context from the parent
The parent design fixes how ID clients and servers stay reachable when UDP is denied — fallback order, broker shapes, trust model, and the E2E boundary. The parent issue carries the surrounding decisions this ticket must not re-decide; where this ticket's answer would change a parent decision, record that explicitly rather than silently forking it.
Decision record expected
Close this design with a recorded decision (on this issue or in a doc/ record linked from it): the chosen shape, the alternatives rejected and why, and the invariants implementation must hold. If the design splits further, file the splits and link them here rather than growing this issue.
Relations
Parent: #5671. Programme: epic #2056. Filed by WS-F (2026-11-04 ID design gap & expansion pass).
This is design work, not a reproducible code defect. Keep the scope to the broker/serve-proxy protocol: TCP/HTTP(S) framing, multiplexing and head-of-line behavior, keepalive/idle-timeouts, and reconnect/resumption. Record the chosen shape, rejected alternatives, and implementation invariants as the issue requires.
Activity
developing-today commentedon Nov 5, 2026
CODE-1475
dezren39 commentedon Nov 5, 2026
Agent note · picked up
dezren39 commentedon Nov 5, 2026
🤖 Agent note · triage complete
Triage of issue #5792 at current main (verified 2026-11-05):
04f78696abfbdf6567f58e623d80520436f002fa; a targeted search found noserve-proxy/id: design: id broker / serve-proxy role (from #5671) #5792 design implementation there, and a fresh PR search for5792 in:bodyreturned none. No hard-stop labels are present.fleet idsurface design. The current id: design: fleet surface for the broker role (from #5671) #5798 triage likewise places id: design: id broker / serve-proxy role (from #5671) #5792 first; id: design: fleet surface for the broker role (from #5671) #5798 should follow the broker-role decision. No code PR or implementation blocker prevents continuing this design ticket.Issue stays OPEN; no follow-up task is needed because #5792 itself is the design work item.