Confirming source-routed multicast is dead on the public Internet

Mailman List Mirror (Read Only)
1

Hey, there's a better way.
Split the movie into segments:
Segment 1: Minute 1.
Segment 2: Minute 2.
Segment 3: Minutes 3,4.
Segment 4: Minutes 5-8.
Segment 5: Minutes 9-16.
etc.
Then send each segment in a loop.
Each receiver receives every loop simultaneously.
Each segment may start receiving part way through, but then it starts again.
By the time a segment needs to play, it is completely received.
A 128 minute movie needs 8 streams.
While waiting for the first minute, you can play ads :slight_smile:
The shorter segments don't need to be sent for long:
Receivers can stop receiving the short segments once they have received one loop of it.
When no receiver is receiving a loop, you can stop sending it.

Regards,
Jakob.

2

Hey,

3

I may have worded up-speed potentially ambiguously, I mean over-speed,
meaning access needs higher than stream bitrate to receive stream of
specific bitrate. In practical world, of course already very
problematic scenario for most NFLX consumers.

4

ok. Play 2 minutes of ads at the start and save a stream.
Play another 2 minutes of ads every 16 minutes, then the maximum number of streams is 4.
The ads can be received in a single stream or be received after the shorter streams have completed.

Regards,
Jakob.

5

You could put this multicast receiver into the last hop before the customer
and then send unicast to the customer.

Regards,
Jakob.