HTTP is already the dominant L4 protocol on the Internet. The future of the Internet no longer relies on TCP since protocols like FTP, Telnet, NetBIOS are fading away. Soon the Internet will be DNS, SSH, NTP but the vast majority of traffic will be HTTP. The List of TCP and UDP port numbers on Wikipedia will soon be irrelevant.
Today, HTTP/2 Protocol is completed the IETF draft and sent to the RFC editor – mnot’s blog: HTTP/2 is Done to be approved as standard joining the less than 100 standards that the IETF has actually completed
- Binary Framing – no more telnet for troubleshooting because its no longer ASCII/UTF
- Three years in development – wide ranging inputs from many stories.
- security and performance enhancements
- Impact on firewalls and proxy servers
- Flow control within the HTTP stream is possible – “QoS over HTTP”
- Encryption is integral to HTTP2 and TLS is the default. Encryption is not mandatory but expected.
- Browsers may only support HTTP2 over TLS
- HTTP2 Header compression. Reduces the headers
Insights into politics of the standards and intervention of AT&T / Ericsson to breach HTTP2 security.
http2 explained – Highly recommended white paper from Daniel that explains the details of HTTP2.
HTTP/2 Home Page on GitHub – This is the home page for HTTP/2, a major revision of the Web’s protocol. It is maintained by the IETF HTTP Working Group.
IETF HTTP Working Group
draft-ietf-httpbis-http2–16 – Hypertext Transfer Protocol version 2
SPDY – SPDY — Google Developers
Home | Open Web Alliance
ATIS “Open Web Alliance” – DOCUMENT CENTER – people who stole encryption from HTTP2 that would have protected users better.
SPDY: An experimental protocol for a faster web – The Chromium Projects
Questions From the Audience
- How is a TLS-only protocol going to affect the efficiency of web caches like Varnish?
- HTTP/2 push can speed up site delivery while avoiding a bundling step. How can we instruct CDNs what to push?
- How do dropped packet impact a single TCP connection protocol compared to a multi connection HTTP/1 transfer?
- HTTP was simple. HTTP/2 seems to require a lot more knowledge to get into. How will this impact future developers?
- What is the state of dev tools for working with HTTP/2 and doing speed comparison while transitioning?
- Will the new ecosystem of HTTP/2 require frontend developers to change their tooling and workflows?