20140809 Meeting Minutes

Agenda

• Design signalling system without server

Serverless Signalling

• WebRTC does not specific signalling to establish peer-to-peer connections (exchange of session description and ICE candidates)
• JavaScript code running in a browser is not allowed to open connection to arbitrary addresses. Thus we can't directly connect to another peer.
• Most solutions use a web server (the one providing the JS code) for signalling but we don't want something centralized.

Pod

Peer-to-peer network of "pods" which allows finding a known user and starting a WebRTC session with that user.

• Pod use:
• is user connected?
• exchange SDP/ICE messages
• serve app code
• DHT storing opaque user id (key) and encrypted status (pod IP, status, etc.)
• No critical info on Pod (proxy only)
• How safe?
• Invitation to session which time out
• Contacts: encrypted & distributed

Next steps

• Implement text chat in palava
• Create the pod system