The Need for Web UDP
&gt; Requirements<p>&gt; 1. Security - it has to benefit from SSL.<p>There is a lot more to security than transport-layer encryption and authentication.<p>&gt; Connection based<p>UDP is too hard, so re-inventing TCP?<p>&gt; p2p is not reliable ... monetization<p>Oh, you want require the SAaSS[1] model.<p>&gt; Simple to use<p>The already-stated &quot;requirements&quot; are asking for something <i>more</i> complex than WebRTC.<p>&gt; Minimum header overhead<p>Wait, are you thinking about using UDP to transport <i>HTTP?!</i> Do you even know what your MTU is?<p>&gt; WebRTC suffers from complexity<p>That complexity exists for reason. Nowhere in this document is a discussion of the potential problems of using UDP or the ways tthe new service might be exploited by malicious actors.<p>[1] Service as a Software Substitute