Ian Swett's research while affiliated with Google Inc. and other places

What is this page?


This page lists the scientific contributions of an author, who either does not have a ResearchGate profile, or has not yet added these contributions to their profile.

It was automatically created by ResearchGate to create a record of this author's body of work. We create such pages to advance our goal of creating and maintaining the most comprehensive scientific repository possible. In doing so, we process publicly available (personal) data relating to the author as a member of the scientific community.

If you're a ResearchGate member, you can follow this page to keep up with this author's work.

If you are this author, and you don't want us to display this page anymore, please let us know.

Publications (1)


Figure 1: QUIC in the traditional HTTPS stack. 
Figure 2: Timeline showing the percentage of Google traffic served over QUIC. Significant increases and decreases are described in Section 5.1. 
Figure 4: Timeline of QUIC's initial 1-RTT handshake, a subsequent successful 0-RTT handshake, and a failed 0-RTT handshake.
Figure 5: Structure of a QUIC packet, as of version 35 of Google's QUIC implementation. Red is the authenticated but unencrypted public header, green indicates the encrypted body. This packet structure is evolving as QUIC gets standardized at the IETF [2].
Figure 6: Search Latency reduction for users in the QUIC experiment over an 18-month period. Numbered events are described in Section 5.2. 

+7

The QUIC Transport Protocol: Design and Internet-Scale Deployment
  • Conference Paper
  • Full-text available

August 2017

·

11,328 Reads

·

685 Citations

Adam Langley

·

Janardhan Iyengar

·

Jeff Bailey

·

[...]

·

Ian Swett

We present our experience with QUIC, an encrypted, multiplexed, and low-latency transport protocol designed from the ground up to improve transport performance for HTTPS traffic and to enable rapid deployment and continued evolution of transport mechanisms. QUIC has been globally deployed at Google on thousands of servers and is used to serve traffic to a range of clients including a widely-used web browser (Chrome) and a popular mobile video streaming app (YouTube). We estimate that 7% of Internet traffic is now QUIC. We describe our motivations for developing a new transport, the principles that guided our design, the Internet-scale process that we used to perform iterative experiments on QUIC, performance improvements seen by our various services, and our experience deploying QUIC globally. We also share lessons about transport design and the Internet ecosystem that we learned from our deployment. This article is summarized in: the morning paper an interesting/influential/important paper from the world of CS every weekday morning, as selected by Adrian Colyer

Download
Share

Citations (1)


... H3 exhibits several notable advantages, such as fast connection, stream multiplexing, better adaptation to network conditions, and improved security [3]- [5]. The superiority of H3 has been widely documented in various scenarios to highlight its ability to reduce latency [6], [7], improve throughput [8], [9], and provide better resilience [4], [10] in emulation and production environments [11], [12]. ...

Reference:

Dissecting the Applicability of HTTP/3 in Content Delivery Networks
The QUIC Transport Protocol: Design and Internet-Scale Deployment