SearcharxivSearch

arXiv · 1906.06153

Do we need two forms of feedback in the Rate Control Protocol (RCP)?

Abstract

There is considerable interest in the networking community in explicit congestion control as it may allow the design of a fair, stable, low loss, low delay, and high utilization network. The Rate Control Protocol (RCP) is an example of such a congestion control protocol. The current design of RCP suggests that it should employ two forms of feedback; i.e. rate mismatch and queue size, in order to manage its flow control algorithms. An outstanding design question in RCP is whether the presence of queue size feedback is useful or not, given feedback based on rate mismatch. In this paper, we address this question using tools from control and bifurcation theory. We linearize the actual non-linear system and analyze the local asymptotic stability, robust stability and rate of convergence of both the design choices, i.e., with and without queue size feedback. But such analyses do not offer clear design recommendations on whether the queue feedback is useful or not. This motivates a bifurcation-theoretic analysis where we have to take non-linear terms into consideration, which helps to learn additional dynamical properties of the RCP system. In particular, we proceed to analyze two non-linear properties, namely, the type of Hopf bifurcation and the asymptotic stability of the bifurcating limit cycles. Analytical results reveal that the presence of queue feedback in RCP can induce a sub-critical Hopf bifurcation, which can lead to undesirable system behavior. Whereas, in the absence of queue feedback, the Hopf bifurcation is always super-critical where the bifurcating limit cycles are stable and of small amplitude. The analysis is corroborated by numerical computations and some packet-level simulations as well. Based on our work, the suggestion for RCP is to only include feedback based on rate mismatch in the design of the protocol.

Explore related subjects

Keep this discovery

BibTeXRIS

Abuthahir Abuthahir, Gaurav Raina, Thomas Voice. 2019-06-13. Do we need two forms of feedback in the Rate Control Protocol (RCP)?. https://arxiv.org/abs/1906.06153

Cite the original work for its findings. Save a collection to share your selection of sources.

KEEP EXPLORING

Related papers

Message-Level Scheduling for RLNC-Coded Multi-Source Traffic

This paper studies weighted decoding-delay minimization for multiple RLNC-coded message streams that compete for finite processing capacity at a destination. Packet arrivals are exogenous, while the scheduler only determines the processing order of packets already available at the destination. A trace-conditioned offline scheduling formulation shows that a batch-release subclass is strongly NP-hard even with a single processing unit. Message-Aware Innovation-Deficit Scheduling (MAIDS) is then developed to prioritize each serviceable message according to its weight and remaining decoding deficit. For a single processing unit, MAIDS is shown to be exactly optimal under nonblocking progressive arrivals with equal weights and under common activation with arbitrary positive weights, while the unrestricted weighted online problem admits no universal deterministic $O(1)$ competitive ratio. Simulation results on streaming and batch benchmarks show that MAIDS consistently reduces weighted decoding delay relative to the tested baselines, remains close to the offline optimum on average, and recovers the predicted exact performance boundaries.

cs.NI

The Towers Were Standing: A Cause Decomposition of Cellular Outages During Hurricane Helene

Hurricane Helene produced the largest absolute cell-site outage in the public FCC record, peaking at 4562 sites. The conventional model is physical: towers destroyed. Helene did destroy over 1700 miles of fibre, but almost none of it was cell sites. We present the first cause-decomposed study of the FCC's Disaster Information Reporting System, reconstructing 80 state-days and 580 county-days from 24 daily filings by two reconciled independent extractions. Damage to cell sites is negligible: 1.1% of attributed cell-site-days across six states, at most 3.8% anywhere. The sites were standing. What took them out divides by terrain: pooled, power dominates at 63.2%, but in mountainous North Carolina severed transport (backhaul) reaches 52.2% against 47.3%, and in Tennessee 69.9%. North Carolina's transport share rises from 7.0% to 85.0% across the event (\r{ho} = 0.92). Seventeen days after landfall, on 15 October, 47 sites lost transport across six contiguous North Carolina counties with no rainfall, no power loss, no damage, and recovery by the next report. Independent active-probe measurement corroborates it: responsive /24s fall 1.02% for twelve hours while Tennessee stays flat. We release the dataset. Backup power is the standard resilience investment; here it addresses the smaller half of the problem.

cs.NI

terms.txt: A Consent and Compensation Protocol for Agentic Web Access

The open web ran on an unwritten bargain: sites admitted crawlers, and search engines sent visitors back. Public measurements show that bargain breaking under AI crawlers and agents. Automated clients now make up most requests, training dominates Cloudflare-classified crawling, and the largest AI platforms fetch thousands of pages for each visitor they return. The web's common control, robots.txt, cannot express identity, purpose, terms, or price, can be circumvented, and newer alternatives are largely proprietary CDN features. We specify terms.txt, a robots.txt-style file for per-path, per-purpose machine-access terms, plus an origin-enforced exchange using Web Bot Auth signatures, signed intent, delegation tokens, HTTP 402 negotiation, and signed receipts. We define what the exchange can enforce, audit, and leave to contract. A dependency-free implementation adds 0.20 to 0.65 ms per request on one vCPU.

cs.NI