WebRTC: Difference between revisions
Jump to navigation
Jump to search
(→WebRTC: move headers up a level so we don't duplicate the page title) |
(UX and security issues) |
||
| Line 3: | Line 3: | ||
See [http://webrtc.org/ WebRTC.org] for general information and pointers. | See [http://webrtc.org/ WebRTC.org] for general information and pointers. | ||
See [[Webcam_Sharing]] for Feature UX and security. | == 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 [http://www.ietf.org/proceedings/81/slides/rtcweb-10.pdf 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 == | == Rough Todo == | ||
Revision as of 20:17, 27 July 2011
See our API Proposal
See WebRTC.org for general information and pointers.
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?
- Consider interaction with browser id, chat
- User-agent vs web content as the bridge initiator?
- How to redirect calls among devices?
- Divide and integrate Google's webrtc code drop
- Network
- Capture Devices
- Codecs/processing