2015
DOI: 10.17487/rfc7424
|View full text |Cite
|
Sign up to set email alerts
|

Mechanisms for Optimizing Link Aggregation Group (LAG) and Equal-Cost Multipath (ECMP) Component Link Utilization in Networks

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1

Citation Types

0
4
0

Year Published

2015
2015
2022
2022

Publication Types

Select...
7
2

Relationship

0
9

Authors

Journals

citations
Cited by 10 publications
(4 citation statements)
references
References 21 publications
0
4
0
Order By: Relevance
“…For comparing the ability of distinct sampling techniques in assisting network flow analysis correctly, several flow parameters are considered, namely: (i) the amount of flows identified; (ii) the percentage of heavy-hitter (HH) flows identified, where the notion of heavy hitter refers to 20% of the largest flows in terms of size (number of packets) [13]; (iii) the utilization share at transport level; (iv) the utilization share at application level; and, (v) the accuracy of load estimations for the identified flows.…”
Section: B Comparative Parametersmentioning
confidence: 99%
“…For comparing the ability of distinct sampling techniques in assisting network flow analysis correctly, several flow parameters are considered, namely: (i) the amount of flows identified; (ii) the percentage of heavy-hitter (HH) flows identified, where the notion of heavy hitter refers to 20% of the largest flows in terms of size (number of packets) [13]; (iii) the utilization share at transport level; (iv) the utilization share at application level; and, (v) the accuracy of load estimations for the identified flows.…”
Section: B Comparative Parametersmentioning
confidence: 99%
“…On the other hand, all the coupled congestion control strategies are designed for connections between the same endpoints having homogeneous round-trip times, and they tend not to fully leverage the statefulness of the TCP congestion control algorithm. Their mechanisms rely on the assumption that connections between the same endpoints share a common bottleneck -this may be true for routers in theory, but in reality two connections may take different routes if they have different TCP port numbers [8].…”
Section: Introductionmentioning
confidence: 99%
“…All the aforementioned approaches have an additional, entirely different problem: they assume that multiple TCP connections sending to the same destination would take the same path. This is not always true -load-balancing mechanisms such as Equal-Cost Multi-Path (ECMP) and LAG [6] may force them to take different paths. Therefore, in this particular scenario, combining the congestion controllers would incur wrong behavior.…”
Section: Introductionmentioning
confidence: 99%