Less-than-Best-Effort Service: A Survey of End-to-End Approaches

Ros, David; Welzl, Michael

doi:10.1109/surv.2012.060912.00176

Cited by 45 publications

(26 citation statements)

References 74 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Rate-based congestion control has been proposed in [34], [43] and has been shown to achieve promising results. Furthermore, detour mechanisms, multipath routing and traffic engineering are well-investigated topics [20], [21], [27].…”

Section: Figure 1: Network Resource Poolingmentioning

confidence: 99%

See 1 more Smart Citation

Revisiting Resource Pooling

Psaras

Saino

Pavlou

2014

Proceedings of the 13th ACM Workshop on Hot Topics in Networks

View full text Add to dashboard Cite

We question the widely adopted view of in-network caches acting as temporary storage for the most popular content in Information-Centric Networks (ICN). Instead, we propose that in-network storage is used as a place of temporary custody for incoming content in a store and forward manner. Given this functionality of in-network storage, senders push content into the network in an open-loop manner to take advantage of underutilised links. When content hits the bottleneck link it gets re-routed through alternative uncongested paths. If alternative paths do not exist, incoming content is temporarily stored in in-network caches, while the system enters a closed-loop, back-pressure mode of operation to avoid congestive collapse.Our proposal follows in spirit the resource pooling principle, which, however, is restricted to end-to-end resources and paths. We extend this principle to also take advantage of in-network resources, in terms of multiplicity of available sub-paths (as compared to multihomed users only) and in-network cache space. We call the proposed principle InNetwork Resource Pooling Principle (INRPP). Using the INRPP, congestion, or increased contention over a link, is dealt with locally in a hop-by-hop manner, instead of end-toend. INRPP utilises resources throughout the network more efficiently and opens up new directions for research in the multipath routing and congestion control areas.

show abstract

Section: Figure 1: Network Resource Poolingmentioning

confidence: 99%

“…These include reactive response to congestion, burstiness, RTT-unfairness, slow flow completion time, flow-synchronisation and inherent ability to clog the network with data and cause congestion [15], [43].…”

Section: Congestion: a Network-layer Problemmentioning

confidence: 99%

Revisiting Resource Pooling

Psaras

Saino

Pavlou

2014

Proceedings of the 13th ACM Workshop on Hot Topics in Networks

View full text Add to dashboard Cite

show abstract

“…The different solutions proposed in literature can be categorized according to three broad approaches: splitconnection, link-layer, and end-to-end approach [4,5]. Split-connection protocols break TCP connection into two parts, at the base station; link-layer variants provide reliability through local retransmissions; finally, in endto-end approaches, the sender performs loss recovery without breaking the semantics of TCP.…”

Section: Introductionmentioning

confidence: 99%

A cross-layer jitter-based TCP for wireless networks

Andreadis

Rizzuto

Zambon

2016

J Wireless Com Network

View full text Add to dashboard Cite

The Transmission Control Protocol (TCP) is one of the main communication protocols in the Internet, and it has been designed to provide an efficient reaction to packet loss events which are due to network congestion. Congestion is the main cause of losses in wired networks, but in today heterogeneous networks, loss events can also be introduced due to higher error rates on wireless channels, host mobility, and frequent handovers. Unfortunately, all packet losses are interpreted by TCP as a sign of congestion, triggering an inappropriate reaction which reduces its transmission rate and leads to performance degradation. In order to avoid this problem, it is important for TCP to correctly understand whether the reason of a packet loss is due to congestion or to a problem in the wireless link. This paper presents an innovative jitter-based cross-layer TCP algorithm, named XJTCP. It adopts the jitter ratio as loss predictor, joined with a layer two notification, in order to correctly infer the nature of a loss event. Performance evaluation and comparison with other common TCP implementations shows how XJTCP can be an interesting solution in the presence of wireless environments.

show abstract

“…Among the different transport protocols providing a LBE service [3], Low Extra Delay Background Transport (LED-BAT) [4] is the most used. LEDBAT is a delay-based congestion control protocol that has been standardized by the Internet Engineering Task Force (IETF).…”

Section: Introductionmentioning

confidence: 99%