An Approach for HTTP 2.0 to Make Mobile Apps and the Web Faster

This week at the IETF meeting on how to approach HTTP 2.0 and improve the Internet. Microsoft will submit a proposal for "HTTP Speed+Mobility." Improving HTTP starts with speed. There is already broad consensus about the need to make web browsing much faster. Improving HTTP should also make mobile better. "The approach we propose focuses […]

This week at the IETF meeting on how to approach HTTP 2.0 and improve the Internet. Microsoft will submit a proposal for "HTTP Speed+Mobility." Improving HTTP starts with speed. There is already broad consensus about the need to make web browsing much faster. Improving HTTP should also make mobile better.

"The approach we propose focuses on all the web's end users - emphasizing performance improvements and security while at the same time accounting for the important needs of mobile devices and applications," Jean Paoli, general manager, Interoperability Strategy, notes in a blog post.

"We think that apps--not just browsers--should get faster too. More and more, apps are how people access web services, in addition to their browser."

"This approach includes keeping people and their apps in control of network access. Specifically, the client remains in control over the content that it receives from the web. This extends a key attribute of the existing HTTP protocol that has served the Web well. The app or browser is in the best position to assess what the user is currently doing and what data is already locally available. This approach enables apps and browsers to innovate more freely, delivering the most relevant content to the user based on the user's actual needs," Paoli continues.

Adding, "To make that happen, HTTP 2.0 needs to retain as much compatibility as possible with the existing Web infrastructure. Awareness of HTTP is built into nearly every switch, router, proxy, load balancer, and security system in use today. If the new protocol is "HTTP" in name only, upgrading all of this infrastructure would take too long. By building on existing web standards, the community can set HTTP 2.0 up for rapid adoption throughout the web," Paoli said.

He further said, "The HTTP Speed+Mobility proposal starts from both the Google SPDY protocol (a separate submission to the IETF for this discussion) and the work the industry has done around WebSockets."

He also highlights the importance of adopting HTTP 2.0 stating, "We are looking forward to a vigorous, open discussion within the IETF around the design of HTTP 2.0. We are excited by the promise of an HTTP 2.0 that will serve the Internet for decades to come," said Paoli.