- From: gmandyam via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Nov 2018 05:01:19 +0000
- To: public-web-and-tv@w3.org
>I fail to see how concerns of OTA broadcast systems relate to actual IP networks. ROUTE, and the way that ATSC profiles it, seems like a fine fit for OTA broadcast. However, things are much different on the real Internet. Do you have any case studies of ROUTE deployments on the Internet? ATSC is an IP Multicast system. What do you consider the "real Internet"? Is ATSC a fake system? >I was part of the DVB analysis and disagree with your statement. The conclusions of ATSC are not applicable to heterogenous IP networks. ATSC is heterogenous. Unicast transport is fully integrated into ATSC along with IP multicast. Your premise is not accurate. >There are some groups interested in replacing the UDP and SCTP aspects of WebRTC for QUIC. It becomes the transport layer for RTP that would allow you to continue using such a FEC scheme. If your organization (or anyone else) is planning to adapt FLEX FEC for QUIC then that would be of interest to many interested parties, not just myself. > Some of the concerns you state are not relevant to a systems that provide both unicast and multicast modes of delivery (in some form of combination that is a deployment/implementation concern.). Again - ATSC does porivde both unicast and multicast modes of delivery. Please familiarize yourself with the specification before making such statements. -- GitHub Notification of comment by gmandyam Please view or discuss this issue at https://github.com/w3c/media-and-entertainment/issues/1#issuecomment-441156838 using your GitHub account
Received on Friday, 23 November 2018 05:01:20 UTC