pm/FURPS/application/signal_network.md

27 lines
959 B
Markdown
Raw Normal View History

2025-06-12 16:45:32 +10:00
# Signal Network PoC FURPS
## Functionality
2025-06-30 15:44:12 +10:00
1. Establish direct connection to remote peer using their public key as identifier.
2025-06-12 16:45:32 +10:00
## Usability
2025-06-30 15:44:12 +10:00
1. Developers can implement their own application-level discovery method.
2. Only remote peer's public key is needed to initiate connection.
3. Hook is provided for developer to filter inbound connection requests.
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.
2025-06-30 15:44:12 +10:00
3. Only 1:1 direct connections are supported.
2025-06-12 16:45:32 +10:00
## + (Privacy, Anonymity, Deployments)
2025-06-30 15:44:12 +10:00
1. Network observers cannot retrieve node connection details; forward secrecy is **not** included.
2025-06-12 16:45:32 +10:00
2. STUN and TURN servers may be required for WebRTC usage.