From 43ddea1b8f37cebf9821acc9cda5c7ada7d1a145 Mon Sep 17 00:00:00 2001 From: fryorcraken Date: Thu, 12 Jun 2025 16:45:32 +1000 Subject: [PATCH] FURPS for signal network --- FURPS/application/signal_network.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 FURPS/application/signal_network.md diff --git a/FURPS/application/signal_network.md b/FURPS/application/signal_network.md new file mode 100644 index 0000000..22dcf8d --- /dev/null +++ b/FURPS/application/signal_network.md @@ -0,0 +1,24 @@ +# Signal Network PoC FURPS + +## Functionality + +1. Establishes a direct connection between two peers using Waku as a signaling layer + +## Usability + +1. Developers have access to a simple API: single entry `connect` function and event-based inbound handling. + +## Reliability + +1. End-to-end reliability is implemented for the signaling conversation. +2. No provided reliability for established connections, left to the developer (e.g. keep alive). + +## Supportability + +1. Developers can use this protocol in web application, imported from npmjs.com. +2. Developers can use this protocol to initiate WebRTC connections. + +## + (Privacy, Anonymity, Deployments) + +1. Signaling payloads are end-to-end encrypted. +2. STUN and TURN servers may be required for WebRTC usage. \ No newline at end of file