To switch or not to switch to TCP Prague? Incentives for adoption in a partial L4S deployment

Fatih Berkay Sarpkaya, Ashutosh Srivastava, Fraida Fund, Shivendra Panwar

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

The Low Latency, Low Loss, Scalable Throughput (L4S) architecture has the potential to reduce queuing delay when it is deployed at endpoints and routers throughout the Internet. However, it is not clear how TCP Prague, a prototype scalable congestion control for L4S, behaves when L4S is not yet universally deployed. Specifically, we consider the question: in a partial L4S deployment, will a user benefit by unilaterally switching from the status quo TCP to TCP Prague? To address this question, we evaluate the performance of a TCP Prague flow when sharing an L4S or non-L4S bottleneck queue with a non-L4S flow. Our findings suggest that the L4S congestion control, TCP Prague, has less favorable throughput or fairness properties than TCP Cubic or BBR in some coexistence scenarios, which may hinder adoption.

Original languageEnglish (US)
Title of host publicationANRW 2024 - Proceedings of the 2024 Applied Networking Research Workshop
PublisherAssociation for Computing Machinery, Inc
Pages45-52
Number of pages8
ISBN (Electronic)9798400707230
DOIs
StatePublished - Jul 23 2024
Event2024 Applied Networking Research Workshop, ANRW 2024 - Vancouver, Canada
Duration: Jul 20 2024Jul 26 2024

Publication series

NameANRW 2024 - Proceedings of the 2024 Applied Networking Research Workshop

Conference

Conference2024 Applied Networking Research Workshop, ANRW 2024
Country/TerritoryCanada
CityVancouver
Period7/20/247/26/24

Keywords

  • AQM
  • Congestion Control
  • L4S
  • Low Latency
  • TCP

ASJC Scopus subject areas

  • Computer Networks and Communications
  • Information Systems

Fingerprint

Dive into the research topics of 'To switch or not to switch to TCP Prague? Incentives for adoption in a partial L4S deployment'. Together they form a unique fingerprint.

Cite this