mirror of
https://github.com/logos-messaging/pm.git
synced 2026-01-02 14:13:09 +00:00
FURPS for signal network
This commit is contained in:
parent
a115762d59
commit
43ddea1b8f
24
FURPS/application/signal_network.md
Normal file
24
FURPS/application/signal_network.md
Normal file
@ -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.
|
||||
Loading…
x
Reference in New Issue
Block a user