This is really a great question that we get all the time. When we talk to IT organizations or CIOs we hear, “Well, I know I’m going to have HTML5 video delivery, but what is it that I want to use for transport? What’s the protocol we’re going to be using?”
The nice thing about having an HTML5 video delivery strategy is it supports all of these protocols. And frankly, it’s going to be the platform you choose that will determine what the protocol is going to be. So, for example, if you’re using Microsoft Stream or Teams or Skype for Business, it’s going to be DASH. You can be using any number of other providers, and they may choose to use DASH. Others, like MediaPlatform, will use HLS.
So, when committing to an HTML5 video delivery environment, you want to choose an underlying eCDN, common enterprise streaming infrastructure, that will support all the HTML5 transport protocols. That way you can deploy your delivery infrastructure once then not worry anymore about the protocol your platforms support.
From the Streaming Media webinar Content Delivery Challenges in a New Era.