lguillory at reservetele.com
Wed Jan 11 18:15:51 UTC 2017
I reached out to my vendor and got back the following. Also what services have you seen move to HTTPS that you're not able to cache?
Regarding HTTPS Streaming and Netflix...
Netflix announced in the spring of 2015 that it would move to HTTPS delivery by April of 2016. At the time of that first announcement, some concluded Netflix might not be able to afford the capital investment required to enable HTTPS delivery.
Given Netflix did not complete the HTTPS project by their first deadline, we believe they have been focused on other priorities such as their global expansion, So, given this history, it's not clear just when or if Netflix will make the move to majority HTTPS for delivery. Furthermore, Netflix is under considerable pressure from investors to improve subscriber growth, revenue growth and profitability. The HTTPS project does not support any of these goals. In fact, Netflix reported net income is marginal and a move to full HTTPS delivery would likely consume all profits for the year.
Along with the rest of the industry, we recognize the need for Open Caching systems to support HTTPS streaming from upstream content providers. This is one of the reasons why we were a Founding Member, along with 16 other streaming companies, in the Streaming Video Alliance in the fall of 2014. The SVA now includes almost 50 member companies from across the streaming ecosystem and around the world. More importantly, the Open Caching Working Group has issued functional requirements, unanimously approved by SVA members, which include support for HTTPS streams.
The SVA Board has invited Netflix to join the Alliance and, in doing so, endorse the Open Caching work underway. This would open up a path in the short run to ensure any open cache can continue to support Netflix content even if Netflix moves to HTTPS delivery. We expect to see Netflix become more active in the SVA soon given other major streaming providers, such as Hulu and Amazon, are joining now.
In conclusion, the SVA has developed a solution for Open Cache support of HTTPS streaming and we expect all streaming providers, including Netflix, will align with the SVA's direction.
Let me know if you have any more questions.
Network Operations Manager
Email: lguillory at reservetele.com
100 RTC Dr
Reserve, LA 70084
The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material which should not disseminate, distribute or be copied. Please notify Luke Guillory immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Luke Guillory therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. .
From: NANOG [mailto:nanog-bounces at nanog.org] On Behalf Of Keenan Singh
Sent: Tuesday, January 10, 2017 10:09 PM
To: nanog at nanog.org
Subject: Bandwidth Savings
We are an ISP in the Caribbean, and are faced with extremely high Bandwidth costs, compared to the US, we currently use Peer App for Caching however with most services now moving to HTTPS the cache is proving to be less and less effective. We are currently looking at any way we can save on Bandwidth or to be more Efficient with the Bandwidth we currently have. We do have a Layer 2 Circuit between the Island and Miami, I am seeing there are WAN Accelerators where they would put a Server on either end and sort of Compress and decompress the Traffic before it goes over the Layer 2, I have never used this before, has any one here used anything like this, what results would I be able to expect for ISP Traffic?
If not any ideas on Bandwidth Savings, or being more Efficient with want we currently.
Many thanks for any Help
More information about the NANOG