WHIP (WebRTC HTTP Ingest Protocol) was developed to bring the advantages of WebRTC to traditional hardware and software encoders, such as a fully encrypted signal path, ultra-low latency, and etc.

Using WHIP vs an external output or NDI to a web browser based ingest tool would make WebRTC connections more solid by eliminating the browser and/or NDI webcam input apps, as well as prevent workarounds to ingest audio when using the external output (such as virtual cables). This also allows us to treat it like a streaming service, keeping the external and NDI outputs available for other needs in a production.

My request is to add the WHIP protocol as a streaming option.

More information about the WHIP protocol:
IETF - https://www.ietf.org/arc...t-ietf-wish-whip-01.html

Millicast (creators of WHIP) https://millicast.medium...edia-ingest-57c2b98fb285

Thanks for your consideration!