@@ -1,83 +0,0 @@
2−title = "WebRTC Gall Agent and external app"
6−grant_type = [ "Proposal" ]
7−grant_category = [ "App Dev" ]
11−description = "Add WebRTC support to Urbit, including call/stream setup and teardown messaging and ICE/STUN/TURN advertisement and authentication."
13−assignee = "Edward Amsden ~ritpub-sipsyl"
21−Adding the ability to make encrypted media calls between Urbit ships, using only Urbit as a signalling channel, without a centralized intermediary, would provide real utility and an immediate boost in the excitement in the end user interface.
23−WebRTC provides media device (camera/speaker/microphone) discovery and peer-to-peer encrypted transit of media. It is supported by all major browsers as well as libraries for many major programming languages.
25−WebRTC relies on external signalling, implemented by the application developer, to handle connection negotiation and call setup and teardown.
27−This creates a natural synergy with URbit, as Urbit provides a hierarchical peer-communication system between known addresses with reputation. A WebRTC Gall agent would provide a solution for coordinating real-time media communications between Urbit ships.
33−This will serve as the _signalling_ channel for Urbit WebRTC applications. WebRTC requires an out-of-band channel (in standard usage usually implemented as an HTTP REST API) which can receive connectivity information from peers and distribute it to peers.
35−### WebRTC calling app
37−This would be an external (probably in-browser) app which would provide the initial end-user interface for
39−- making two-way media calls
40−- making n-way media conference calls
41−- streaming media from one peer to many
43−### ICE/STUN/Turn advertising
45−A separate Gall agent would initially allow stars to advertise ICE and STUN servers for use by sponsored planets and their moons. WebRTC depends on ICE and STUN to allow NATed and firewalled peers to negotiate peer-to-peer connections.
47−The last milestone would be to add TURN advertising with authentication to this agent. TURN servers provide relay services for peers which cannot directly connect, thus they are much more expensive, especially in terms of bandwidth, than ICE and and STUN. This should permit stars to specify which planets are authorized to use the TURN server, and, in the planet instantiation of the agent, seamlessly offer this information to WebRTC and other applications using the agent.
51−The proposer would eventually like to see media streas themselves propagated via Urbit. To achieve this, however,
52−it would be necessary to:
54−- Create a performant method (likely a vane) for passing network messages which are not retained in the event log
55−- Significantly improve Urbit's NAT traversal and firewall hole-punching abilities to match the state of the art.
56− (this has been discussed with, among others, ~ritfed-tabrg and ~wolref-podlex).
60−Edward Amsden ~ritpub-sipsyl is a vertan software developer and principal of Black River Software. He has spent the last 5+ years working on industrial IoT solutions in Haskell as a contractor for Plow Technologies.
64−[Mozilla Developer Network WebRTC walkthrough](https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/Signaling_and_video_calling)
65−[Dealing with connectivity](https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/Connectivity)
69−### Gall agents (WebRTC, ICE/STUN)
72−A Gall agent which handles exchanging SDP messages for WebRTC applications
73−Another Gall agent which handles advertising ICE and STUN servers from stars to planets
75−### Standalone WebRTC-via-Urbit app
78−Urbit app running in browser and hosted/interfaced via Eyre which provides the three categories of calling functionality described in the body of the proposal
80−### Authenticated TURN advertising
83−Extension of the ICE/STUN Gall agent to allow stars to advertise an authenticated TURN server to some or all of their sponsored planets. Extension of the WebRTC application to use TURN servers.