1. RTC-Web Framework Jonathan Rosenberg Chief Technology Strategist, Skype

2. Base Case (Model 1) Browser JS/HTML App Application Provider JS API Media + Media Path Signaling (ICE/STUN/TURN) Proprietary Over HTTP/Websocket Proprietary Over HTTP/Websocket

3. Base Case (Model 2) Browser JS/HTML App Application Provider JS API Media + Media Path Signaling (ICE/STUN/TURN) Standardized Signaling

4. API as Protocol App Provider Web Server App Provider Web Server Caller Javascript Callee Javascript Caller Browser Callee Browser JS API JS API App Trust Domain Browser Trust Domain Media + Media Path Signaling (ICE/STUN/TURN)

5. API Scope Caller Javascript Caller Browser JS API Media + Media Path Signaling (ICE/STUN/TURN) P2P Connection Management FW/NAT Traversal Control Codec capabilities and selection Media control Codec control Media security Data Transfer P2P Connection Management FW/NAT Traversal Control Codec capabilities and selection Media control Codec control Media security Data Transfer

6. Security Problem 1: DDoS App Provider Web Server App Provider Web Server Caller Javascript Caller Browser DDoS Target JS API App Trust Domain Browser Trust Domain Media + Media Path Signaling (ICE/STUN/TURN) Malicious Website

7. Security Problem 2: Protocol Emulation App Provider Web Server App Provider Web Server Caller Javascript Caller Browser Corporate DNS Server JS API App Trust Domain Browser Trust Domain Browser packets emulating DNS Malicious Website

8. Provider Interop Case Browser JS/HTML App Application Provider 1 JS API Media + Media Path Signaling (ICE/STUN/TURN) Application Provider 1 SIP

9. Existing Gear Case 1 Browser JS/HTML App Application Provider 1 JS API Media + Media Path Signaling (ICE/STUN/TURN) SIP IP PBX SIP, MGCP, H323, Proprietary

10. Existing Gear Case 2 Browser JS/HTML App Application Provider 1 Media + Media Path Signaling (ICE/STUN/TURN) SIP IP PBX SIP, MGCP, H323, Proprietary Media Gateway Media Gateway