BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Https - the solution to net neutrality and ISP monopolies
- Subject: [Discuss] Https - the solution to net neutrality and ISP monopolies
- From: richard.pieri at gmail.com (Richard Pieri)
- Date: Sat, 26 Jul 2014 23:16:25 -0400
- In-reply-to: <06f44e7cf55941c6a9ef176fee54df0e@CO2PR04MB684.namprd04.prod.outlook.com>
- References: <8a6a33076074465486f84ce055503bbc@CO2PR04MB684.namprd04.prod.outlook.com> <Pine.NEB.4.64.1407261031430.1770@panix2.panix.com> <06f44e7cf55941c6a9ef176fee54df0e@CO2PR04MB684.namprd04.prod.outlook.com>
On 7/26/2014 10:57 PM, Edward Ned Harvey (blu) wrote: > Yup, but remember there are two possible explanations why: Neither of which are at all relevant. All Netflix traffic is encrypted but this did not prevent Comcast from intentionally degrading Netflix traffic throughput. All Netflix traffic is encrypted but this does not prevent the choke point between Level 3 and Verizon from degrading all traffic including Netflix. A choke point can only be routed around by literally routing around it. It's not the encryption provided by the VPN that provides such routing. It's the routing itself. -- Rich P.
- References:
- [Discuss] Https - the solution to net neutrality and ISP monopolies
- From: blu at nedharvey.com (Edward Ned Harvey (blu))
- [Discuss] Https - the solution to net neutrality and ISP monopolies
- From: sronan at panix.com (Stephen Ronan)
- [Discuss] Https - the solution to net neutrality and ISP monopolies
- From: blu at nedharvey.com (Edward Ned Harvey (blu))
- [Discuss] Https - the solution to net neutrality and ISP monopolies
- Prev by Date: [Discuss] Https - the solution to net neutrality and ISP monopolies
- Next by Date: [Discuss] php dev's code with warnings and notices
- Previous by thread: [Discuss] Https - the solution to net neutrality and ISP monopolies
- Next by thread: [Discuss] any decent NTFS implementations for Linux?
- Index(es):
