Real-time Audio-Visual Media Transport over QUIC

Perkins, Colin; Ott, Jörg

doi:10.1145/3284850.3284856

Cited by 15 publications

(9 citation statements)

References 29 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…QUIC itself [1] has been the topic of several papers, focusing on its deployment and performance on the Internet [41,42], especially for media traffic [43,44,45] and some of its core components, such as its security [46] and multipath [47,48] frameworks.…”

Section: Future and Related Workmentioning

confidence: 99%

Towards Securing the Internet of Things with QUIC

Eggert¹

2020

Proceedings 2020 Workshop on Decentralized IoT Systems and Security

View full text Add to dashboard Cite

This paper is the first to evaluate the feasibility of deploying QUIC, a new UDP-based transport protocol currently undergoing IETF standardization, directly on resourceconstrained IoT devices. It quantifies the storage, compute, memory and energy requirements of the Quant QUIC stack on two different IoT platforms, and finds that a minimal standardscompliant QUIC client currently requires approximately 58 to 63 KB of flash and can retrieve 5 KB of data in 4.2 to 5.1 s over 0-RTT or 1-RTT connections, using less than 16 KB of heap memory (plus packet buffers), less than 4 KB of stack memory and less than 0.9 J of energy per transaction.1 The Argon includes an additional 4 MB of flash that is accessible over an SPI bus, but that can only be used to store data, not code (this memory is used to emulate the EEPROM).

show abstract

Section: Future and Related Workmentioning

confidence: 99%

Towards Securing the Internet of Things with QUIC

Eggert¹

2020

Proceedings 2020 Workshop on Decentralized IoT Systems and Security

View full text Add to dashboard Cite

show abstract

“…However, because these studies do not consider network conditions such as the throughput, loss ratio and the number of concurrent connections, aggressive downloads can lead to excessive competition and performance degradation. In Reference [23,24], QUIC was extended to support partial reliable transmission for the performance enhancement of multimedia applications. In partial reliable transmission, essential data were transmitted reliably and, less important data were transmitted unreliably to avoid retransmission.…”

Section: Related Workmentioning

confidence: 99%

“…However, latency reduction in the QUIC protocol is limited because it also sets a small initial congestion window and employs slow start. Several studies have been conducted focusing on performance improvement, implementation validation and security [19][20][21][22][23][24][25][26][27][28]. Among these studies, some authors have proposed latency reduction schemes for QUIC.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Access Latency Reduction in the QUIC Protocol Based on Communication History

Jung¹,

2019

Electronics

View full text Add to dashboard Cite

Internet traffic is experiencing rapid growth, with the majority of traffic generated from video steaming, web data services and Internet of Things. As these services include the transmission of small data, such as web pages, video chunks and sensing data, data latency affects the quality of experience rather than the throughput. Therefore, this study aims to decrease latency to improve the quality of the user experience. To this end, we measure the web service delay and throughput in mobile networks. The results indicate a low quality experience for mobile users, even though mobile networks support a large throughput. We therefore propose a light-weight latency reduction scheme for the Quick UDP Internet Connections (QUIC) protocol. The proposed scheme calculates the average congestion window, which is utilized as the initial congestion window when a new connection is established. The proposed scheme is evaluated through experiments on a testbed. The results show that our scheme reduces latency significantly. The results of this study can help improve user experiences of video streaming and web data services.

show abstract

“…Partial reliability with optional timelined data meets the requirements of all three categories. Whether these features come as core part of the protocol or through extensions [63], it is pertinent that past mistakes are not repeated and future infrastructures and networks are built with this flexibility in mind. Encrypted headers within QUIC protocol could prevent against ossification caused by middleboxes, however, deployability is also affected by infrastructure and API support, which is still possible.…”

Section: Visions For Futurementioning

confidence: 99%