I completely agree. W3C seems to be always behind reality, trying to describe it, but not define it. IETF did a lot of very useful work, but they have been branching out into rather obscure protocols recently. Where is HTTP/1.2? Surely HTTP/1.1 is not perfect?
And Google did what Google does: they threw together a prototype and checked how it would work. And it seems it is working very well for them, but maybe not so much for others.
I would also advocate to separate some of the concerns. Transmitting huge amount of bulk data is a problem that is (mostly) solved with HTTP/1.1. Encryption less so, session tracking is a bit of a pain, and server push is really ugly in HTTP/1.1.
PS: Concerning the original submission, there is nothing wrong with encrypting cookies. Instead it is the proper thing to do if you do not trust the client, which you should never do.