[163989] in North American Network Operators' Group
Re: net neutrality and peering wars continue
daemon@ATHENA.MIT.EDU (Neil Harris)
Sat Jun 22 15:07:15 2013
Date: Sat, 22 Jun 2013 20:06:25 +0100
From: Neil Harris <neil@tonal.clara.co.uk>
To: Owen DeLong <owen@delong.com>
In-Reply-To: <12C00316-E6F8-45A9-8B4A-081A39E6F20D@delong.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 22/06/13 16:34, Owen DeLong wrote:
>>> That's easily solved by padding the ACK to 1500 bytes as well.
>>>
>>> Matt
>>>
>> Or indeed by the media player sending large amounts of traffic back to the CDN via auxiliary HTTP POST requests?
>>
>> Neil
>>
>>
>>
> That would assume that the client has symmetrical upstream bandwidth over which to send such datagrams. At least in the US, that is the exception, not the rule.
>
> Owen
>
>
Hi Owen,
You only need to match the video stream bandwidth, not the full download
speed of the link.
Given that current multicore CPUs are now fast enough to decode HEVC in
software, and with HEVC being roughly twice as efficient as H.264, that
means you should be able to do quite decent full HDTV quality video with
an average bandwdith of about 5 Mbps, given sufficient buffering to
smooth out the traffic. Less, if you're willing to compromise on picture
quality a bit, and go for, say, 720p.
So, given an HEVC-capable decoder, this strategy should work for any
connection with an upstream speed of better than about 4 to 5 Mbps,
which is becoming more and more common on cable Internet service, as
DOCSIS 3.0 is rolled out and faster links become more common,
Neil
