MétaCan
Menu
Back to cohort
Record W2058665619 · doi:10.1109/ciss.2008.4558690

Can API-RCP be TCP friendly with RED?

2008· article· en· W2058665619 on OpenAlexaff
Yang Hong, Oliver Yang

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicNetwork Traffic and Congestion Control
Canadian institutionsUniversity of Ottawa
Fundersnot available
KeywordsBottleneckRouterComputer scienceNetwork congestionComputer networkActive queue managementTCP Friendly Rate ControlQueueing theoryBandwidth (computing)QueueThe InternetCUBIC TCPRandom early detectionRobustness (evolution)Distributed computingNetwork packetOperating systemEmbedded system

Abstract

fetched live from OpenAlex

TCP is widely implemented for congestion control in current IP networks. As the network bandwidth increases, TCP becomes oscillatory and prone to instability, regardless of the queuing scheme. As a rate-based control scheme, XCP was proposed to obtain high link utilization in high bandwidth-delay product networks, while maintaining small queue size in the routers. XCP explicit feedbacks the congestion information in the bottleneck link to the source, and brings a flurry of research interests recently. However, XCP cannot settle to zero steady-state error due to the capacity estimation error, and may lead to arbitrarily low link utilization. Using solid control theoretical analysis and design, API-RCP has solved the potential problems of XCP successfully. Furthermore, API-RCP has simpler structure for real-time implementation. Due to its satisfactory transient network performance and its stability robustness to the dramatic change of the network traffic, API-RCP is a promising algorithm for practical implementation. Why can API-RCP solve the modeling deficiency of XCP? Can API-RCP be TCP friendly with TCP/RED (the current dominant congestion control mechanism in the Internet) in the same router? To answer these two questions, we have made control theoretical comparison of API-RCP with XCP and run OPNET simulation when the APIRCP and TCP/RED co-exist in the same router.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.933
Threshold uncertainty score0.327

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.012
GPT teacher head0.190
Teacher spread0.178 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations7
Published2008
Admission routes1
Has abstractyes

Explore more

Same topicNetwork Traffic and Congestion ControlFrench-language works237,207