From: Filippov Alexey Date: Wednesday, July 22, 2015 at 1:18 PM To: "Ali C. Begen", "[email protected]<mailto:[email protected]>" Subject: RE: [video-codec] draft-filippov-netvc-requirements-01
From the codec point of view the only difference between “IPTV” and “IP video”(OTT, OpenIPTV, etc.) is managed or unmanaged network (i.e. error robustness). Correct? Nope. In IPTV, the bandwidth is provisioned so you know your packets will not really face a loss or large delay unless something really bad happens. In IP video, there are no such guarantees, anything can happen to your packets. Thus, IP/OTT video uses mostly TCP (with HTTP). Such apps have entirely different set of goals to optimize (or trade off) compared to IPTV apps. If so, we can consider these two applications as a single use-case with a requirement for error resilience if the network is unmanaged. In my view, neither IPTV nor IP/OTT video should be error resilient. They should be error free, that is it. But to me, skype, conferencing, rtcweb must be error resilient, especially when running over non-QoS networks. In this case, my main question is whether you mind to consider OTT video as a use case for NETVC codec or not? As I said, it should not be the focus at the moment, later a different profile can be developed as needed.
_______________________________________________ video-codec mailing list [email protected] https://www.ietf.org/mailman/listinfo/video-codec
