Design P2P networking architecture and domain model #3

New issue

Open

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

emidab commented

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

Owner

Summary

Design the network architecture and shared abstractions for P2P discovery and mTLS-secured streaming before any concrete networking work. This is the contract the child/parent and streaming issues build on.

What to do

Choose the P2P discovery mechanism (WiFi P2P / peer discovery) matching the platforms
Define the connection lifecycle: discover → pair → handshake (QR) → connect → stream → reconnect/degrade
Sketch the mTLS cert/identity model (self-signed, no central CA, cert pinning via QR)
Define core domain model: Device, Role (child/parent), Session, StreamType
Document the design in docs/architecture/ and reference it from README

Acceptance criteria

Discovery approach documented and justified (offline-first, no server)
Connection lifecycle has explicit states and failure handling
mTLS trust model described (QR-exchanged fingerprints, no CA)
Core domain entities defined and agreed
Architecture doc linked from README

Notes

No cloud/server — everything must work peer-to-peer over WiFi
This issue produces a design document + domain model, not implementation
Implementation lives in the networking feature issues that reference this

## Summary Design the network architecture and shared abstractions for P2P discovery and mTLS-secured streaming before any concrete networking work. This is the contract the child/parent and streaming issues build on. ## What to do 1. Choose the P2P discovery mechanism (WiFi P2P / peer discovery) matching the platforms 2. Define the connection lifecycle: discover → pair → handshake (QR) → connect → stream → reconnect/degrade 3. Sketch the mTLS cert/identity model (self-signed, no central CA, cert pinning via QR) 4. Define core domain model: Device, Role (child/parent), Session, StreamType 5. Document the design in `docs/architecture/` and reference it from README ## Acceptance criteria - [ ] Discovery approach documented and justified (offline-first, no server) - [ ] Connection lifecycle has explicit states and failure handling - [ ] mTLS trust model described (QR-exchanged fingerprints, no CA) - [ ] Core domain entities defined and agreed - [ ] Architecture doc linked from README ## Notes - No cloud/server — everything must work peer-to-peer over WiFi - This issue produces a design document + domain model, not implementation - Implementation lives in the networking feature issues that reference this