Fatih Berkay Sarpkaya
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Research Interests
Fatih Berkay Sarpkaya has a total of 3 co-authors. Here are the top co-authors by number of shared publications:
- Fraida Fund
New York University, New York, NY, USA
2 shared publications - Shivendra S. Panwar
Department of Electrical and Computer Engineering, New York University Tandon School of Engineering, Brooklyn, NY, USA
2 shared publications - Ashutosh Srivastava
New York University, Brooklyn, NY, USA
1 shared publication
Latest Publications
- 7 March 2025
- Published by Springer Nature
- p. 217-246
To Adopt or Not to Adopt L4S-Compatible Congestion Control? Understanding Performance in a Partial L4S Deployment
- 7 March 2025
- Published by Springer Nature
- p. 217-246
To Adopt or Not to Adopt L4S-Compatible Congestion Control? Understanding Performance in a Partial L4S Deployment
- Open Access
- 20 July 2024
- Published by Association for Computing Machinery (ACM)
- p. 45-52
To switch or not to switch to TCP Prague? Incentives for adoption in a partial L4S deployment
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.
- 20 July 2024
- Published by Association for Computing Machinery (ACM)
- p. 45-52
Open AccessTo switch or not to switch to TCP Prague? Incentives for adoption in a partial L4S deployment
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.