Re: Call for Consensus (CfC): WebRTC-NV Use Cases

A very belated response:



>  1. Section 3.2: Low latency P2P broadcast:
>     https://w3c.github.io/webrtc-nv-use-cases/#auction
>     <https://w3c.github.io/webrtc-nv-use-cases/#auction>
>
>
>
I support the inclusion of this use case, with the understanding that 
"broadcast" means "semi-simultaneous unidirectional delivery of the same 
audio/video content to a number of users beyond 1000".


>
>  2. Section 3.4: Decentralized Internet:
>     https://w3c.github.io/webrtc-nv-use-cases/#decent
>     <https://w3c.github.io/webrtc-nv-use-cases/#decent>
>
>
I support the inclusion of this use case. I note that if a service 
worker can create an RTCPeerConnection, this is trivially implementable.


>  3. Section 3.9: Reduced complexity signaling:
>     https://w3c.github.io/webrtc-nv-use-cases/#urisig
>     <https://w3c.github.io/webrtc-nv-use-cases/#urisig>
>
I support the inclusion of this use case.

However, the resulting requirement may be too simplistic due to the 
abuse possibilities outlined in RFC 8827 - in particular, it violates 
section 6.3 of that document. Therefore, I do not support including 
requirement N39 as written; unless we also change RFC 8827, the 
requirement should be phrased differently.