WebRTC
Jump to navigation
Jump to search
See WebRTC.org for general information and pointers.
See our API Proposal
Roc is working on the MediaStream Processing API proposal.
UI Issues
See Webcam_Sharing for Feature UX and security around enabling cameras and mics.
Security
Security will be a tough problem due to conflicting use-case requirements. See IETF Security Considerations for an overview of some of the issues.
Main topics:
- camera/mic enabling (and disabling)
- avoidance of accidental/tricked/malicious calling
- security of other information stored in the browser in the face of a rough rtcweb app or compromised server.
Rough Todo
Items we're thinking about
- Codec options: base of G.711 (free subset), Opus, VP8.
- Do we want to support any others? G.722, iLBC, iSAC?
All of those are free with no patent issues.
- Do we want to support any others? G.722, iLBC, iSAC?
- Consider interaction with BrowserId, chat
- User-agent vs web content as the bridge initiator?
- How to redirect calls among devices?
- Fork (offer connect to person at desktop, laptop, mobile at once)
- Forward (device-based, provider-based) of incoming connections
- Transfer (move connection to another device or person)
- Divide and integrate Google's webrtc code drop
- Network
- Capture Devices
- Codecs/processing