This document discusses HTTP/2 and QUIC protocols. It provides an overview of HTTP/1.1 limitations and how HTTP/2 addresses these through features like request multiplexing and header compression. It also introduces QUIC as a new protocol developed by Google that aims to reduce latency through connection migration and security integration. The document recommends tracking QUIC's development at the IETF and provides links to resources about web performance bottlenecks and browser support for these protocols.

1. bdNOG 6 – Bogra, Bangladesh

2. https://www.netcraft.com/internet-data-mining/taxonomy-of-internet-services-companies/

3. http://www.smartinsights.com/mobile-marketing/mobile-marketing-analytics/mobile-
marketing-statistics/attachment/mobile-share-of-online-time-percent-2017/

6. Performance
Matters ...

10. GET
POST
HEAD
HTTP 0.9 HTTP 1.0
PUT
DELETE
LINK
UNLINK

14. So HTTP 1.1 has Flaws ?

16. https://hpbn.co/primer-on-web-performance/#latency-as-a-performance-bottleneck

21. Single

22. TTFB
++

35. One request, many responses
Ability to “PUSH” a resource to the client
before the client requests it

38. Need to have HTTPS URLs
Uses TLS extension ALPN

42. http://caniuse.com/#search=http%2F2

47. Q U I C

49. Track the development of QUIC
https://datatracker.ietf.org/wg/quic/charter