[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Confirming source-routed multicast is dead on the public Internet
- Subject: Confirming source-routed multicast is dead on the public Internet
- From: jheitz at cisco.com (Jakob Heitz (jheitz))
- Date: Thu, 2 Aug 2018 21:56:32 +0000
- In-reply-to: <CAAeewD98MTA=9i-J0gEPUhkUQFUXC8GwPC=oH3XhwNA3Hu9T1A@mail.gmail.com>
- References: <[email protected]> <CAAeewD-Gm+7Wgv-LxpTGZt6LZCzYLQB_=HkKfT3_kWo=gecZ+A@mail.gmail.com> <CAAeewD98MTA=9i-J0gEPUhkUQFUXC8GwPC=oH3XhwNA3Hu9T1A@mail.gmail.com>
You could put this multicast receiver into the last hop before the customer
and then send unicast to the customer.
Regards,
Jakob.
-----Original Message-----
From: Saku Ytti <saku at ytti.fi>
Sent: Thursday, August 2, 2018 2:45 PM
To: Jakob Heitz (jheitz) <jheitz at cisco.com>
Cc: nanog at nanog.org
Subject: Re: Confirming source-routed multicast is dead on the public Internet
On Fri, 3 Aug 2018 at 00:42, Saku Ytti <saku at ytti.fi> wrote:
> Cute :). Well 8*bitrates, but nice optimisation to make stream count
> finite. Of course at cost of quality, as receiver needs up-speed of 8x
> at start. Interesting side-effect, quality increases as movie
> progresses :)
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.
--
++ytti