Investigate WebRTC for flash proxy NAT punching

hellais suggested WebRTC (http://www.webrtc.org/, https://en.wikipedia.org/wiki/WebRTC) as a way to directly connect browsers behind NATs. This could be useful for the JavaScript flash proxy, which otherwise doesn't work at all when the censored user is behind NAT.

We should examine WebRTC to find out at least

How much information it discloses to a third party. (For facilitation of NAT punching, for example. This was a problem with the Adobe RTMFP transport in the Flash-based proxy.)

How common it is or can be expected to become; i.e., will a censor be reluctant to block it wholesale.

What are the implications for protocol fingerprinting.

What browsers it is supported in.

How easy it is to implement and deploy.

WebRTC API http://dev.w3.org/2011/webrtc/editor/webrtc.html
Architecture http://www.webrtc.org/reference/architecture note references to STUN and ICE.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information