As has been pointed out, this is a little more complicated than just
the choice of client, in particular multicast is not widely available
to the "average" Internet user.
that could be punctuated very differently and thus become even more factual.
But I still find it ironic that I can watch a webcast from an ICANN
meeting but I am unable to do the same for an IETF meeting (until after
the fact). That is but one example.
well, let's do what we always do, then... have a BOF about it. we can wire
a 1394 camera to jabber somehow, but until there's widely deployed idmr or
a whole lot of widely deployed open/shared L4 streamsplitters, this won't
be a protocol problem (like it ought to be).
for dark humour value, i note with dispair that in 1992 when i participated in
a project at DEC (r.i.p.) to move the nasdaq trading system onto tcp/ip, we
were told by several people that "ya oughta use multicast". my part of the
project was an L4 streamsplitter that was used because multicast didn't work.
folks told us that we'd regret it and have to tear it out in a year or two
when multicast became widely deployed. someone, somewhere, is probably still
using "DECrbs" because for them, multicast still isn't a realistic possibility.
--
Paul Vixie