[186725] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Netflix stuffing data on pipe

daemon@ATHENA.MIT.EDU (Matt Hoppes)
Wed Dec 30 07:42:37 2015

X-Original-To: nanog@nanog.org
From: Matt Hoppes <mhoppes@indigowireless.com>
In-Reply-To: <20151230075950.GA32240@slab-wks-04.int.slabnet.com>
Date: Wed, 30 Dec 2015 07:42:33 -0500
To: Hugo Slabbert <hugo@slabnet.com>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

I'm not buffering. Switches have packet buffers. I'm seeing switch buffers g=
etting overrun by what appears to be Netflix traffic coming in at rates fast=
er than the subscribers throttled speeds.=20

> On Dec 30, 2015, at 02:59, Hugo Slabbert <hugo@slabnet.com> wrote:
>=20
>> On Tue 2015-Dec-29 21:17:51 -0600, Josh Reynolds <josh@kyneticwifi.com> w=
rote:
>>=20
>> The second part. Fixed wireless is not even on their radar.
>>> On Dec 29, 2015 9:16 PM, "Matt Hoppes" <mhoppes@indigowireless.com> wrot=
e:
>>>=20
>>> So they are trying to stuff every last bit as an end device modulates up=

>>> and down?
>>>=20
>>> Or are you saying that's how they determine if they can scale up the
>>> resolution "because there is more throughout available now".
>>>=20
>>> On Dec 29, 2015, at 22:10, Josh Reynolds <josh@kyneticwifi.com> wrote:
>>>=20
>>> Adaptive bandwidth detection.
>>>> On Dec 29, 2015 8:59 PM, "Matt Hoppes" <mhoppes@indigowireless.com> wro=
te:
>>>>=20
>>>> Has anyone else observed Netflix sessions attempting to come into
>>>> customer CPE devices at well in excess of the customers throttled plan?=

>>>>=20
>>>> I'm not talking error retries on the line. I'm talking like two to thre=
e
>>>> times in excess of what the customers CPE device can handle.
>>>>=20
>>>> I'm observing massive buffer overruns in some of our switches that appe=
ar
>>>> to be directly related to this. And I can't figure out what possible go=
od
>>>> purpose Netflix would have for attempting to do this.
>=20
> Pardon my ignorance of WISP-specific bits here, but how are they supposed t=
o know to back off on their bitrate ramp-up if you keep buffering rather tha=
n dropping packets when the TX rate exceeds the customer's service rate?  Or=
 what am I missing?
>=20
>>>> Curious if anyone else has seen it?
>=20
> --=20
> Hugo
>=20
> hugo@slabnet.com: email, xmpp/jabber
> PGP fingerprint (B178313E):
> CF18 15FA 9FE4 0CD1 2319 1D77 9AB1 0FFD B178 313E
>=20
> (also on Signal)
>=20

home help back first fref pref prev next nref lref last post