[opendtv] Re: TV Technology: Korea to Launch ATSC 3.0 Broadcasts in 2017
- From: "Manfredi, Albert E" <albert.e.manfredi@xxxxxxxxxx>
- To: "opendtv@xxxxxxxxxxxxx" <opendtv@xxxxxxxxxxxxx>
- Date: Fri, 26 Feb 2016 02:02:49 +0000
Craig Birkmaier wrote:
You mean the context I have been claiming is possible for several
years; the same context you have claimed is not possible with IP?
I mean, in the context that you know enough to understand what the words mean.
It's just like SFNs. A superficial understanding of the marketing hype does not
translate to being able to make intelligent comments on deployment realities.
In this case, the mention of "IP" seems to fool you into believing that a
one-way IP pipe is enough to do everything you're used to doing on the
Internet. 2 + 2 = 5. But that's totally false. Please inform yourself, and
reading RFC 6726 is a start.
Funny how the impossible has now become possible
Again, you have to inform yourself first. After you have informed yourself,
answer me this very simple question:
List the functionality you can get from FLUTE that you cannot get from ATSC 1.0
with MPEG-2 TS and, ultimately, MPEG-2 TS plus ATSC A/90. Just name one service
that FLUTE will support, that ATSC 1.0 cannot support.
The problem with superficial understandings is that you attribute meanings, to
the words in the marketing hype, that simply do not apply. You see "IP," and
you think web browsing, email, and all the rest. But it doesn't work that way.
Many times! To be precise you have always argued that IP requires
a two way pipe.
And it does. It EVEN DOES for FLUTE. The main purpose of FLUTE is to enable use
of IP multicast for file transfers to a huge number of clients. Answer these
questions:
1. How does your PC find out about the FLUTE session, if it can't use some of
those techniques listed in RFC 6726, such as HTTP (or email)?
2. How does your PC join the multicast group, indicated by those other
techniques, if it can't signal upstream to its router? (Look up IGMP.)
3. How do the multicast routers communicate with one another, to build
multicast trees? (Look up PIM-SM or PIM-SSM, for instance).
The presumption in FLUTE is that the computer is connected to a two-way network
anyway. So sure, you can use the purely one-way aspect of FLUTE, for a one-way
broadcast. But the restrictions that imposes are such that you can do exactly
the same thing with ATSC 1.0 already. If you doubt this, give me an example
where it's not the case.
You can't do a web session over FLUTE, for example.
I have known that this has been possible for years Bert.
You've "known" nothing of the sort. Look up HTTP (RFC 7540 for the new
version), and show me how it is a one-way protocol. Or just use simple logic.
With a one-way pipe, explain to us, Craig, how that one-way pipe predicts that
I want to search for ancient Mayan artifacts, at this instant in time.
It cannot. The best you can do is store some broadcast on your premises, and
then have the storage device recreate an HTTP session with your PC. Which can
be done just as easily with ATSC 1.0.
But go ahead and answer my questions above.
Bert
----------------------------------------------------------------------
You can UNSUBSCRIBE from the OpenDTV list in two ways:
- Using the UNSUBSCRIBE command in your user configuration settings at
FreeLists.org
- By sending a message to: opendtv-request@xxxxxxxxxxxxx with the word
unsubscribe in the subject line.
Other related posts:
