mrbluze writes:
"A modified HTTP protocol is being proposed (the proposal is funded by AT&T) which would allow ISP's to decrypt and re-encrypt traffic as part of day to day functioning in order to save money on bandwidth through caching. The draft document states:
To distinguish between an HTTP2 connection meant to transport "https" URIs resources and an HTTP2 connection meant to transport "http" URIs resource, the draft proposes to 'register a new value in the Application Layer Protocol negotiation (ALPN) Protocol IDs registry specific to signal the usage of HTTP2 to transport "http" URIs resources: h2clr.
The proposal is being criticized by Lauren Weinstein in that it provides a false sense of security to end users who might believe that their communications are actually secure. Can this provide an ISP with an excuse to block or throttle HTTPS traffic?"
(Score: 5, Insightful) by caseih on Monday February 24 2014, @07:25PM
Wow, the summary the submitter posted here on soylent, and the headline was quite a bit more clear and lucid than the one that appeared on slashdot yesterday. Kudos. Hope this is the trend and norm on soylent.
The slashdot headline was, "Most Alarming: IETF Draft Proposes 'Trusted Proxy' In HTTP/2.0" which while accurate, wasn't very informative to me.
(Score: 4, Funny) by Bill, Shooter Of Bul on Monday February 24 2014, @08:29PM
Its a miracle it was even accurate.