On Sun, Dec 11, 2011 at 10:46 PM, Faisal Imtiaz <fai...@snappydsl.net> wrote: > Simple, keep traffic off paid ip transit circuits.... >
(I think joel's point was: "peer with amazon, done-and-done") > Faisal > > On Dec 11, 2011, at 10:21 PM, Joel Jaeggli <joe...@bogus.com> wrote: > >> Netflix uses CDNs for content delivery and the platform runs in EC2. What >> would peering with them achieve? >> >> Sent from my iPhone >> >> On Dec 11, 2011, at 18:06, Faisal Imtiaz <fai...@snappydsl.net> wrote: >> >>> Which leads to a question to be asked... >>> >>> Is netflix willing to peer directly with ISP / NSP's ? >>> >>> Regards. >>> >>> Faisal Imtiaz >>> Snappy Internet& Telecom >>> >>> >>> On 12/11/2011 7:29 PM, Dave Temkin wrote: >>>> Feel free to contact peering@netflix<dot>com - we're happy to provide you >>>> with delivery statistics for traffic terminating on your network. >>>> >>>> Regards, >>>> -Dave Temkin >>>> Netflix >>>> >>>> On 12/7/11 8:57 AM, Blake Hudson wrote: >>>>> Yeah, that's an interesting one. We currently utilize netflow for this, >>>>> but you also need to consider that netflix streaming is just port 80 www >>>>> traffic. Because netflix uses CDNs, its difficult to pin down the traffic >>>>> to specific hosts in the CDN and say that this traffic was netflix, while >>>>> this traffic was the latest windows update (remember this is often a >>>>> shared hosting platform). We've done our own testing and have come to a >>>>> good solution which uses a combination of nbar, packet marking, and >>>>> netflow to come to a conclusion. On a ~160Mbps link, netflix peaks out >>>>> between 30-50Mbps around 8-10PM each evening. The rest of the traffic is >>>>> predominantly other forms of HTTP traffic (including other video >>>>> streaming services). >>>>> >>>>> >>>>> Martin Hepworth wrote the following on 12/3/2011 2:36 AM: >>>>>> Also checkout Adrian Cockcroft presentations on their architecture which >>>>>> describes how they use aws and CDns etc >>>>>> >>>>>> Martin >>>>>> >>>>>> >>>>> >>>> >>>> >>>> >>> >> >
