Abstract
QUIC, fostered by Google and under standardization in the IETF, integrates some of HTTP/s, TLS, and TCP functionalities over UDP. One of its main goals is to facilitate transport protocol design, with fast evolution and innovation. However, congestion control in QUIC is still severely jeopardized by packet losses, despite implemented loss recovery mechanisms, whose behavior strongly depends on the Round Trip Time. In this paper, we design and implement rQUIC, a framework that enables FEC within QUIC protocol to improve its performance over wireless networks. The main idea behind rQUIC is to reduce QUIC's loss recovery time by making it robust to erasures over wireless networks, as compared to traditional transport protocol loss detection and recovery mechanisms. We evaluate the performance of our solution by means of extensive simulations over different type of wireless networks and for different applications. For LTE and Wifi networks, our results illustrate significant gains of up to 60% and 25% savings in the completion time for bulk transfer and web browsing, respectively.
Highlights
Quick UDP Internet Connections (QUIC) [1] is an experimental transport protocol designed to primarily reduce connection establishment and transport latencies, as well as to improve security standards with default end-to-end encryption in HTTP-based applications
We carried out an extensive simulation campaign, where we examine the benefits of rQUIC compared to default QUIC, under different network configurations, changing bandwidth, end-to-end delay, and random loss parameters
Implemented in user space, QUIC [2] runs encapsulated inside UDP and it is inspired by best practices of several protocols and extensions such as TCP, TLS 1.3 and HTTP/2
Summary
Quick UDP Internet Connections (QUIC) [1] is an experimental transport protocol designed to primarily reduce connection establishment and transport latencies, as well as to improve security standards with default end-to-end encryption in HTTP-based applications. QUIC’s development had to take a different approach to avoid imminent ossification, i.e. inability to deploy updates and fixes. In case of packet loss, only streams with frames in the lost packets are blocked, leaving others unaffected This is one of the main benefits of QUIC, as it avoids HoL-blocking with multiple streams. Every transmitted packet, including retransmissions, carries a different number, avoiding TCP’s retransmission ambiguity and so simplifying loss detection. Another fundamental difference lies in the Acknowledgment (ACK) frames, which carry multiple ACK blocks and information to yield a more precise RTT estimation. Even though QUIC runs encapsulated inside UDP, all data is reliably transmitted due to the stream and connection flow control [13], and congestion control [14]. The congestion control relies on Cubic, with pacing applied at the sender
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
