From d7ebccb4c50948920b8f4443d32f923ac370c044 Mon Sep 17 00:00:00 2001 From: fryorcraken Date: Fri, 20 Jun 2025 18:41:39 +1000 Subject: [PATCH] Update Signal Network FURPS Trying to be more detailed on expectations to match a recently expressed user need. --- FURPS/application/signal_network.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/FURPS/application/signal_network.md b/FURPS/application/signal_network.md index 22dcf8d..8c9d30d 100644 --- a/FURPS/application/signal_network.md +++ b/FURPS/application/signal_network.md @@ -1,12 +1,17 @@ # Signal Network PoC FURPS +TODO: Update in deliverable + ## Functionality -1. Establishes a direct connection between two peers using Waku as a signaling layer +1. Advertise intent to join a given meeting. +2. Discover remote peers willing to join a given meeting. +3. Establish direct connection to remote peer with same intent to join a given meeting. ## Usability -1. Developers have access to a simple API: single entry `connect` function and event-based inbound handling. +1. Developers sets arbitrary meeting identifier. +2. Developers selects discovered to connect to. ## Reliability @@ -20,5 +25,5 @@ ## + (Privacy, Anonymity, Deployments) -1. Signaling payloads are end-to-end encrypted. +1. Network observers cannot retrieve node connection details without knowing meeting identifier. 2. STUN and TURN servers may be required for WebRTC usage. \ No newline at end of file