Re: HTTP 2.0 mandatory security vs. Amateur Radio

The technical problem is that entities are attempting to be helpful
(sometimes attempting to help the users, and some attempt to help
themselves), and are either failing to adapt with the protocol, or failing
to properly implement it.
Given that putting everything under one roof is infeasible/impossible (the
internet spans many different jurisdictions/countries), and given that we
cannot dictate what people deploy or not, the one technical approach that
has the highest chance of success is the one where content is encrypted.
Do I love this? Nah. But I've been unable to come up with a better plan
that would work. Can you come up with a plan that will work reliably?

-=R


On Thu, Nov 14, 2013 at 4:41 PM, Bruce Perens <bruce@perens.com> wrote:

>  On 11/14/2013 04:28 PM, Ryan Hamilton wrote:
>
>
>  Plain-text HTTP/1 is reliable (as Roberto said).  However plain-text of
> any other protocol on port 80 (WebSockets, HTTP/2.x etc) is *not* reliable
> because of middle boxes that attempt to process that traffic as HTTP/1.
>
> Nothing new will ever work unless we tunnel it opaquely through port 443.
>
> And who thinks this is sustainable?
>
> We should either work out how we can go forward, or put the phone company
> back in charge and get everything from one source again.
>
>     Thanks
>
>     Bruce
>