WebRTC DHT support

[dave-hansen]

Lets discuss the potential of DHT support. WebRTC has some pretty serious restrictions on data transferred and a bit of de-risking should be taken when planning.

How would the DHT features be delivered without UDP or some sort of hand-rolled proprietary, routing outside of the protocol spec?

[diffalot]

i believe we can change the specs, but implementation first. i suspect making WebSockets work over UDP is going to be a harder sell to W3C and partners, but it's still possible.

so, which would be best: adapting DHT to work over TCP, adapting WebSockets to work over UDP, or building an open source UDP <--> TCP proxy service?

[feross]

The current plan is to run the DHT protocol over WebRTC, minus the UDP requirement. We'll just keep open connections to every peer in the DHT routing table. So, hopefully we can keep the modifications minor. Eventually, we hope that we can extend the spec to bridge the gap between normal and web clients.

[feross]

Updated the readme file with more details on how we're doing DHT over WebRTC: eed07d7

[feross]

Let's use this issue for tracking WebRTC DHT support.