...and good for that. Bad standards arise from committees sitting around spit-balling ideas. Good standards come from committees blessing existing practices already proven in the field. Maybe you smooth out a rough spot or two, but ultimately it ought to look for the most part like what's already out there working well. "Not in scope" was precisely the right response for most of the junk people wanted to throw into HTTP/2.0. Alas, it does give people who didn't their favorite feature thrown in ample opportunity to whine. Kamp's whining has the wonderful virtue of being amusingly self-contradictory. "History has shown overwhelmingly that if you want to change the world for the better, you should deliver good tools for making it better, not policies for making it better." Exactly. Trying to improve the world by setting policy via IETF standards, though, is exactly what the IETF did not do in this case, by not adding those things he thinks should be used as a matter of course, and that's what's making Kamp so mad.