About: Performance-enhancing proxy is a research topic. Over the lifetime, 119 publications have been published within this topic receiving 4801 citations.
TL;DR: The results show that a reliable link-layer protocol that is TCP-aware provides very good performance and it is possible to achieve good performance without splitting the end-to-end connection at the base station.
Abstract: Reliable transport protocols such as TCP are tuned to perform well in traditional networks where packet losses occur mostly because of congestion. However, networks with wireless and other lossy links also suffer from significant losses due to bit errors and handoffs. TCP responds to all losses by invoking congestion control and avoidance algorithms, resulting in degraded end-to end performance in wireless and lossy systems. We compare several schemes designed to improve the performance of TCP in such networks. We classify these schemes into three broad categories: end-to-end protocols, where loss recovery is performed by the sender; link-layer protocols that provide local reliability; and split-connection protocols that break the end-to-end connection into two parts at the base station. We present the results of several experiments performed in both LAN and WAN environments, using throughput and goodput as the metrics for comparison. Our results show that a reliable link-layer protocol that is TCP-aware provides very good performance. Furthermore, it is possible to achieve good performance without splitting the end-to-end connection at the base station. We also demonstrate that selective acknowledgments and explicit loss notifications result in significant performance improvements.
TL;DR: This document is a survey of Performance Enhancing Proxies often employed to improve degraded TCP performance caused by characteristics of specific link environments, for example, in satellite, wireless WAN, and wireless LAN environments.
Abstract: This document is a survey of Performance Enhancing Proxies (PEPs) often employed to improve degraded TCP performance caused by characteristics of specific link environments, for example, in satellite, wireless WAN, and wireless LAN environments. Different types of Performance Enhancing Proxies are described as well as the mechanisms used to improve performance. Emphasis is put on proxies operating with TCP. In addition, motivations for their development and use are described along with some of the consequences of using them, especially in the context of the Internet.
TL;DR: This document outlines possible TCP enhancements that may allow TCP to better utilize the available bandwidth provided by networks containing satellite links.
Abstract: This document outlines possible TCP enhancements that may allow TCP to better utilize the available bandwidth provided by networks containing satellite links. The algorithms and mechanisms outlined have not been judged to be mature enough to be recommended by the IETF. The goal of this document is to educate researchers as to the current work and progress being done in TCP research related to satellite networks.
TL;DR: This roadmap provides a brief summary of the documents defining TCP and various TCP extensions that have accumulated in the RFC series and serves as a guide and quick reference for both TCP implementers and other parties who desire information contained in the TCP-related RFCs.
Abstract: This document contains a roadmap to the Request for Comments (RFC)
documents relating to the Internet's Transmission Control Protocol
(TCP). This roadmap provides a brief summary of the documents defining
TCP and various TCP extensions that have accumulated in the RFC
series. This serves as a guide and quick reference for both TCP
implementers and other parties who desire information contained in the
TCP-related RFCs. This document obsoletes RFC 4614.
TL;DR: This document outlines the changes required to use CoAP over TCP, TLS, and WebSockets transports and formally updates RFC 7641 for use with these transports and RFC 7959 to enable the use of larger messages over a reliable transport.
Abstract: The Constrained Application Protocol (CoAP), although inspired by
HTTP, was designed to use UDP instead of TCP. The message layer of
CoAP over UDP includes support for reliable delivery, simple
congestion control, and flow control. Some environments benefit from
the availability of CoAP carried over reliable transports such as TCP
or Transport Layer Security (TLS). This document outlines the changes
required to use CoAP over TCP, TLS, and WebSockets transports. It also
formally updates RFC 7641 for use with these transports and RFC 7959
to enable the use of larger messages over a reliable transport.