> IETF had no option to but to start a standardisation process around HTTP/2 otherwise SPDY would have become a de-facto standard. As is SPDY is becoming the d

> IETF had no option to but to start a standardisation process around HTTP/2 otherwise SPDY would have become a de-facto standard. As is SPDY is becoming the de-facto standard. If this is the role the IETF wants to relegate itself to, just slapping an "Approved" sticker on existing de-facto standards, then the IETF is already irrelevant. I think a better role for the IETF would be to define best practices for the industry to work toward rather than simply describing what has already happened. > PHK has been telling everyone what's wrong with the current HTTP/2 approach since he beginning but with the exception of his session stuff has never really come up with any detail on what should be done different. Opportunistic encryption. AFAIK PHK hasn't said anything about this, but only because he doesn't need to: it's the obvious giant hole in the standard. A few people have already proposed solutions.