
RTC-Web Framework Jonathan RosenbergChief Technology Strategist, Skype
Base Case (Model 1) ApplicationProvider Proprietary Over HTTP/Websocket Proprietary Over HTTP/Websocket JS/HTMLApp JS/HTMLApp JS API Browser Browser Media + Media PathSignaling (ICE/STUN/TURN)
Base Case (Model 2) ApplicationProvider StandardizedSignaling StandardizedSignaling JS/HTMLApp JS/HTMLApp JS API Browser Browser Media + Media PathSignaling (ICE/STUN/TURN)
API as Protocol CallerJavascript App Provider Web Server CalleeJavascript App Trust Domain Browser Trust Domain JS API JS API CallerBrowser CalleeBrowser Media + Media PathSignaling (ICE/STUN/TURN)
API Scope CallerJavascript P2P Connection Management FW/NAT Traversal Control Codec capabilities and selection Media control Codec control Media security Data Transfer JS API CallerBrowser Media + Media PathSignaling (ICE/STUN/TURN)
Security Problem 1: DDoS CallerJavascript App Provider Web Server MaliciousWebsite App Trust Domain Browser Trust Domain JS API CallerBrowser DDoSTarget Media + Media PathSignaling (ICE/STUN/TURN)
Security Problem 2: Protocol Emulation CallerJavascript App Provider Web Server MaliciousWebsite App Trust Domain Browser Trust Domain JS API CallerBrowser CorporateDNS Server Browser packets emulatingDNS
Provider Interop Case ApplicationProvider 1 ApplicationProvider 1 SIP JS/HTMLApp JS/HTMLApp JS API Browser Browser Media + Media PathSignaling (ICE/STUN/TURN)
Existing Gear Case 1 ApplicationProvider 1 IP PBX SIP JS/HTMLApp SIP,MGCP, H323,Proprietary JS API Browser Media + Media PathSignaling (ICE/STUN/TURN)
Existing Gear Case 2 ApplicationProvider 1 IP PBX SIP Media Gateway JS/HTMLApp SIP,MGCP, H323,Proprietary Browser Media + Media PathSignaling (ICE/STUN/TURN)