Reviews:
 ·Cox HSI
 ·VOIPo
| reply to HarpSupport
Re: [CT] Netflix SuperHD? Not here in NOVA.
Has Cox Communications put a press release out on this? I agree that the big HSI companies will hold out on "Open Connect" because of their own OnDemand type offerings.
Ironically, the reason I dropped my DTV was Cox couldn't give me a quality picture at 720, or steady PQ. I've never had even the merest a hiccup with streaming Vudu HDX - The bandwidth is there!
Which makes me wonder... why does Netflix need an "Open Connect" and HSI providers cooperation when other streaming services don't?
--
Cox Preferred HSI~SB6120~Grandstream HT502~E4500
OTA (...and proud of it!)
VOIPo |
|
| Because of the bandwidth caps I believe. Netflix want a way for cable providers to not enforce bandwidth caps on Netflix streaming and Super HD is Netflix's leverage it appears. |
|
|
|
 NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:9
2 edits | reply to dlarkin_dc
Working up a better explanation; should also apply to the respondent to your post. |
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:9 Reviews:
 ·SONIC.NET
·Pacific Bell - SBC
| reply to Foxbat121
I wonder. I was fooling around, but think I got it wrong the first time.
While running a Hulu clip, I ran 'netstat -aon' and came up with:
TCP 192.168.42.36:50700 209.170.97.214:443 ESTABLISHED 3644
TCP 192.168.42.36:50722 17.149.36.185:5223 ESTABLISHED 1916
TCP 192.168.42.36:54128 198.87.182.173:80 ESTABLISHED 4568
TCP 192.168.42.36:54188 173.228.66.8:80 ESTABLISHED 3960
TCP 192.168.42.36:54190 173.228.66.10:80 ESTABLISHED 3960
TCP 192.168.42.36:54195 74.125.224.131:80 ESTABLISHED 3960
TCP 192.168.42.36:54197 173.228.66.10:80 ESTABLISHED 3960
TCP 192.168.42.36:54198 173.228.66.9:80 ESTABLISHED 3960
209.170.97.214 appears to be Akami in Los Angeles, California:
NetRange 209.170.97.0 - 209.170.97.255
CIDR 209.170.97.0/24
Name AKAMAI
Handle NET-209-170-97-0-1
Parent TELIANET-2BLK (NET-209-170-64-0-1)
Most likely the streaming server for Hulu. Trace route shows:
Tracing route to 209.170.97.214 over a maximum of 30 hops
1 <1 ms <1 ms 1 ms 192.168.42.1
2 26 ms 25 ms 26 ms 173-228-7-1.dsl.static.sonic.net [173.228.7.1]
3 25 ms 24 ms 25 ms gig1-4.cr1.lsatca11.sonic.net [70.36.243.13]
4 25 ms 25 ms 24 ms 0.xe-5-1-0.gw.pao1.sonic.net [69.12.211.1]
5 25 ms 25 ms 25 ms 0.xe-6-1-0.gw2.200p-sf.sonic.net [64.142.0.109]
6 26 ms 26 ms 25 ms as0.gw.200p-sf.sonic.net [208.106.96.249]
7 25 ms 26 ms 26 ms xe-10-1-0.bar2.SanFrancisco1.Level3.net [4.53.134.9]
8 27 ms 28 ms 27 ms ae-6-6.ebr2.SanJose1.Level3.net [4.69.140.154]
9 29 ms 27 ms 27 ms ae-92-92.csw4.SanJose1.Level3.net [4.69.153.30]
10 32 ms 27 ms 26 ms ae-4-90.edge2.SanJose3.Level3.net [4.69.152.209]
11 26 ms 46 ms 26 ms sjo-bb1-link.telia.net [213.248.98.29]
12 36 ms 36 ms 37 ms las-bb1-link.telia.net [80.91.247.170]
13 37 ms 36 ms 36 ms 209.170.97.214
Trace complete.
So Hulu content apparently requires leaving Sonic.net (my ISP) transit to traverse Level 3 and Telia to reach the Hulu content.
My understanding of Netflix "Open Connect" is that Netflix places their streaming servers directly on the ISP transit network, such that traversal of third party transit is not necessary.
I need to set up a Netflix account to test this.
Sonic.net, LLC is ready!
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
| Anyone actually used SuperHD yet? How is it? Much different than normal netflix HD streams? |
|
| reply to NormanS
said by NormanS:IMy understanding of Netflix "Open Connect" is that Netflix places their streaming servers directly on the ISP transit network, such that traversal of third party transit is not necessary.
Not necessary. See the technical explanation here:
»signup.netflix.com/openconnect |
|
| reply to Needleinthha
IIRC, Super HD is merely 5.8 mbps. Not exactly will be Blu Ray like quality which are typically 20 to 30 mbps. |
|
| 5.8mbps is certainly not blu-ray but compared to netflix's regular HD superHD is remarkably better. |
|
