> On Mar 22, 2020, at 15:49 , Mark Tinka <mark.ti...@seacom.mu> wrote:
>
>
>
> On 23/Mar/20 00:19, Randy Bush wrote:
>
>>
>> add to that it is the TV model in a VOD world. works for sports, maybe,
>> not for netflix
>
> Agreed - on-demand is the new economy, and sport is the single thing
> still propping up the old economy.
>
> When sport eventually makes into the new world, linear TV would have
> lost its last legs.
How do you see that happening? Are people going to stop wanting to watch live,
or are teams going to somehow play asynchronously (e.g. Lakers vs. Celtics,
the Lakers play on November 5 at 6 PM and the Celtics play on November 8
at 11 AM)?
Further, it would be more accurate to say that events with large live audiences
are the only thing propping up the “old economy” and sport is probably by far
the largest current application of live streaming.
Remember, this discussion started with a question about live-streaming church
services.
In the “new normal” of a COVID lockdown world, with the huge increase in
teleconferencing, etc. there may well be additional audiences for many-to-many
multicast that aren’t currently implemented.
IMO, the only sane way to do this also helps solve the v4/v6 conferencing
question.
Local Aggregation Points (LAPs) are anycast customer terminations. Backbone
between
LAPs supports IPv6-only and IPv6 multicast (intra-domain only). LAPs are not
sharing
routing table space with backbone routers. Likely some tunnel mechanism is used
to
link LAPs to each other to shield backbone routers from multicast state
information.
Each “session” (whether an individual chat, group chat, etc.) gets a unique IPv6
multicast group. Each LAP with at least one user logged into a given session
will
join that multicast group across the backbone. Users connects to LAPs via
unicast.
If voice, video, slide, chat streams need to be separated, use different port
numbers
to do that.
IPv4 nat traversal for the IPv4-only clients is left as an exercise for the
reader.
Owen
