2025-06-12 16:45:32 +10:00
|
|
|
# Signal Network PoC FURPS
|
|
|
|
|
|
2025-06-20 18:41:39 +10:00
|
|
|
TODO: Update in deliverable
|
|
|
|
|
|
2025-06-12 16:45:32 +10:00
|
|
|
## Functionality
|
|
|
|
|
|
2025-06-23 10:02:52 +10:00
|
|
|
1. Advertise intent to join a given session.
|
2025-06-23 10:08:29 +10:00
|
|
|
2. Discover remote peers willing to join a given session.
|
|
|
|
|
3. Establish direct connection to remote peer with same intent to join a given session.
|
2025-06-12 16:45:32 +10:00
|
|
|
|
|
|
|
|
## Usability
|
|
|
|
|
|
2025-06-24 12:12:52 +10:00
|
|
|
1. Developers selects discovered nodes to connect to.
|
2025-06-12 16:45:32 +10:00
|
|
|
|
|
|
|
|
## 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)
|
|
|
|
|
|
2025-06-23 10:08:29 +10:00
|
|
|
1. Network observers cannot retrieve node connection details without knowing session identifier.
|
2025-06-12 16:45:32 +10:00
|
|
|
2. STUN and TURN servers may be required for WebRTC usage.
|
