>The problem is SDP. SDP wasn't originally designed for browser-to-browser communications, and some of the things that WebRTC uses it for go above and beyond th

>The problem is SDP. SDP wasn't originally designed for browser-to-browser communications, and some of the things that WebRTC uses it for go above and beyond the specification. But SDP is just session description. In a way just metadata, so to speak. Hardly a big part of webRTC specification. Ok, there are some rules that govern how to choose appropriate codec and similar, which may seem complicated (but in my opinion aren't - I've worked with SIP for many years), but it seems way overboard to submit your own specification just for SDP. I think it would be many times better to try to influence webRTC specs than splitting the effort and almost certainly prolonging adoption.