2 ms·
You may well see standards bodies that way, but it's pretty common for standards setters to refuse to stamp something unless it is already deployed. Otherwise y
by mike_hearn 12y ago
You may well see standards bodies that way, but it's pretty common for standards setters to refuse to stamp something unless it is already deployed. Otherwise you can get design-by-committee and things that don't solve real world problems.
The role of the IETF is to provide a neutral forum in which protocols can be developed. That means SPDY -> HTTP/2 is an improvement, because now development will be driven via the normal IETF process and forums. But if a committee went off and designed some dream protocol and browser makers/site operators did their own thing, it'd be for naught.
Re: opportunistic SSL, I'd like to see this too, but it's a complex issue and I defer to the judgement of browser developers on that. It isn't something someone who isn't implementing should try and force on industry de jure.