Remix.run Logo
Serving Netflix Video Traffic at 400Gb/S and Beyond (2022) [pdf](nabstreamingsummit.com)
17 points by tosh an hour ago | 8 comments
shanemhansen 11 minutes ago | parent | next [-]

Just an interesting observation I had about this once when I noticed that kernel quic implementations weren't very fast.

KTLS is mostly useful if paired with sendfile (I'm ignoring io_uring because I'm not as up to date on that). Otherwise you have to context switch back to userspace constantly.

comment0r an hour ago | parent | prev | next [-]

Assuming the files are encrypted anyway for DRM reasons: why should static content like movies be TLSed? I know I know, "TLS all the things", but it sounds like a high cost at Netflix scale.

keane 14 minutes ago | parent | next [-]

To prevent a browser mixed content warning maybe (I didn't attend the presentation: https://www.youtube.com/watch?v=WzfADu1qyAM). Apparently 15% of Netflix viewing happens in browsers.

Inside an Apple TV app, the default requires TLS 1.2 or later and while exceptions are apparently allowed (including for media streaming) they are discouraged and require a justification for App Store review: https://developer.apple.com/documentation/security/preventin...

xxpor 26 minutes ago | parent | prev | next [-]

Stops Comcast from seeing the metadata and knowing exactly what their mutual customers are streaming.

booi 16 minutes ago | parent [-]

wait till you hear about what smart tvs do..

the-smug-one 12 minutes ago | parent [-]

I refused to connect my TV to the internet and use a Vero V for all of my watching needs. The Vero V is absolutely worse than most other experiences, but I'm happy.

monocasa 38 minutes ago | parent | prev [-]

It seems like it took engineering work, but TLS isn't their bottleneck when the data flow is structured correctly for the hardware (which is kind of the thesis of a lot of the Netflix CDN node optimization stuff).

DeathArrow 25 minutes ago | parent | prev [-]

Nice seeing BSD s getting some use.