I am often asked why the Internet HTTP community is working on an IETF based QUIC when HTTP/2 (RFC 7540) is less than 2 years old. There are good answers! This work is essentially part two of a planned evolution to improve speed, reliability, security, responsiveness, and architecture. These needs were understood when HTTP/2 was standardized but the community decided to defer larger architectural
![On The Merits of QUIC for HTTP](https://cdn-ak-scissors.b.st-hatena.com/image/square/dbf054a4cbaeea367db92029769422c865cee6a7/height=288;version=1;width=512/https%3A%2F%2Fblogger.googleusercontent.com%2Fimg%2Fb%2FR29vZ2xl%2FAVvXsEhJizJezvpRjfTM1kwTSwVppsG4c_mL_Ly1K9gYFzsLIt_Rx-wcqYE-aJNmfvPW7Kvf-KfSIlJywtJLtziDYvZbxC2cgZ3NDaUM3ZaKv1B0yOej9HylBRJmd0XqR0z1LJ3Sqpfr1bYQgss%2Fw1200-h630-p-k-no-nu%2FQUIC-q.png)