Implement mTLS-secured stream transport and connection lifecycle #6

New issue

Open

opened 2026-09-02 15:25:43 +02:00 by emidab · 0 comments

emidab commented

2026-09-02 15:25:43 +02:00

Owner

Summary

Transport for the actual media and telemetry data. Define and implement the secure payload channel the child→parent streams ride on, so the pair/light issues have a concrete transport.

What to do

Define stream payload protocol (audio frames, video frames, sensor samples)
Implement the mTLS-secured transport using the pinned identities from pairing
Implement the connection lifecycle states from the architecture doc
Provide backpressure/flow control so one stream doesn't starve others
Define and emit structured telemetry metadata per stream

Acceptance criteria

Payload framing protocol documented
Transport uses mTLS with the pinned cert from QR pairing
Connection lifecycle (discover → connect → stream → drop) implemented
Independent streams don't block each other
Transport is testable headless with a fake socket/transport

Notes

Depends on networking architecture and pairing/mTLS issues
This is the concrete transport; media codecs/specifics may be separate issues (split if too large)

## Summary Transport for the actual media and telemetry data. Define and implement the secure payload channel the child→parent streams ride on, so the pair/light issues have a concrete transport. ## What to do 1. Define stream payload protocol (audio frames, video frames, sensor samples) 2. Implement the mTLS-secured transport using the pinned identities from pairing 3. Implement the connection lifecycle states from the architecture doc 4. Provide backpressure/flow control so one stream doesn't starve others 5. Define and emit structured telemetry metadata per stream ## Acceptance criteria - [ ] Payload framing protocol documented - [ ] Transport uses mTLS with the pinned cert from QR pairing - [ ] Connection lifecycle (discover → connect → stream → drop) implemented - [ ] Independent streams don't block each other - [ ] Transport is testable headless with a fake socket/transport ## Notes - Depends on networking architecture and pairing/mTLS issues - This is the concrete transport; media codecs/specifics may be separate issues (split if too large)