m (Scipediacontent moved page Draft Content 938265251 to Prasad Dovrolis 2007a) |
|||
| Line 3: | Line 3: | ||
A TCP flow is congestion responsive because it reduces its send window upon the appearance of congestion. An aggregate of nonpersistent TCP flows, however, may not be congestion responsive, depending on whether the flow (or session) arrival process reacts to congestion or not. In this paper, we describe a methodology for the passive estimation of traffic congestion responsiveness. The methodology aims to classify every TCP session as either "open-loop" or "closed-loop". In the closed-loop model, the arrival of a session depends on the completion of the previous session from the same user. When the network is congested, the arrival of a new session from that user is delayed. On the other hand, in the openloop model, TCP sessions arrive independently of previous sessions from the same user. The aggregate traffic that the open-loop model generates is not congestion responsive, despite the fact that each individual flow in the aggregate is congestion responsive. Our measurements at a dozen of access and core links show that more than 60-80% of the traffic that we could analyze (mostly HTTP traffic) follows the closed-loop model. | A TCP flow is congestion responsive because it reduces its send window upon the appearance of congestion. An aggregate of nonpersistent TCP flows, however, may not be congestion responsive, depending on whether the flow (or session) arrival process reacts to congestion or not. In this paper, we describe a methodology for the passive estimation of traffic congestion responsiveness. The methodology aims to classify every TCP session as either "open-loop" or "closed-loop". In the closed-loop model, the arrival of a session depends on the completion of the previous session from the same user. When the network is congested, the arrival of a new session from that user is delayed. On the other hand, in the openloop model, TCP sessions arrive independently of previous sessions from the same user. The aggregate traffic that the open-loop model generates is not congestion responsive, despite the fact that each individual flow in the aggregate is congestion responsive. Our measurements at a dozen of access and core links show that more than 60-80% of the traffic that we could analyze (mostly HTTP traffic) follows the closed-loop model. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| Line 15: | Line 10: | ||
* [http://www.cc.gatech.edu/fac/Constantinos.Dovrolis/Papers/pam07-ravi.pdf http://www.cc.gatech.edu/fac/Constantinos.Dovrolis/Papers/pam07-ravi.pdf] | * [http://www.cc.gatech.edu/fac/Constantinos.Dovrolis/Papers/pam07-ravi.pdf http://www.cc.gatech.edu/fac/Constantinos.Dovrolis/Papers/pam07-ravi.pdf] | ||
| + | |||
| + | * [http://link.springer.com/content/pdf/10.1007/978-3-540-71617-4_18.pdf http://link.springer.com/content/pdf/10.1007/978-3-540-71617-4_18.pdf], | ||
| + | : [http://dx.doi.org/10.1007/978-3-540-71617-4_18 http://dx.doi.org/10.1007/978-3-540-71617-4_18] | ||
| + | |||
| + | * [https://link.springer.com/chapter/10.1007%2F978-3-540-71617-4_18 https://link.springer.com/chapter/10.1007%2F978-3-540-71617-4_18], | ||
| + | : [https://www.scipedia.com/public/Prasad_Dovrolis_2007a https://www.scipedia.com/public/Prasad_Dovrolis_2007a], | ||
| + | : [https://dblp.uni-trier.de/db/conf/pam/pam2007.html#PrasadD07 https://dblp.uni-trier.de/db/conf/pam/pam2007.html#PrasadD07], | ||
| + | : [https://doi.org/10.1007/978-3-540-71617-4_18 https://doi.org/10.1007/978-3-540-71617-4_18], | ||
| + | : [https://dl.acm.org/citation.cfm?id=1762912 https://dl.acm.org/citation.cfm?id=1762912], | ||
| + | : [https://rd.springer.com/chapter/10.1007/978-3-540-71617-4_18 https://rd.springer.com/chapter/10.1007/978-3-540-71617-4_18], | ||
| + | : [https://academic.microsoft.com/#/detail/1587450584 https://academic.microsoft.com/#/detail/1587450584] | ||
Latest revision as of 16:07, 21 January 2021
Abstract
A TCP flow is congestion responsive because it reduces its send window upon the appearance of congestion. An aggregate of nonpersistent TCP flows, however, may not be congestion responsive, depending on whether the flow (or session) arrival process reacts to congestion or not. In this paper, we describe a methodology for the passive estimation of traffic congestion responsiveness. The methodology aims to classify every TCP session as either "open-loop" or "closed-loop". In the closed-loop model, the arrival of a session depends on the completion of the previous session from the same user. When the network is congested, the arrival of a new session from that user is delayed. On the other hand, in the openloop model, TCP sessions arrive independently of previous sessions from the same user. The aggregate traffic that the open-loop model generates is not congestion responsive, despite the fact that each individual flow in the aggregate is congestion responsive. Our measurements at a dozen of access and core links show that more than 60-80% of the traffic that we could analyze (mostly HTTP traffic) follows the closed-loop model.
Original document
The different versions of the original document can be found in:
- https://www.scipedia.com/public/Prasad_Dovrolis_2007a,
- https://dblp.uni-trier.de/db/conf/pam/pam2007.html#PrasadD07,
- https://doi.org/10.1007/978-3-540-71617-4_18,
- https://dl.acm.org/citation.cfm?id=1762912,
- https://rd.springer.com/chapter/10.1007/978-3-540-71617-4_18,
- https://academic.microsoft.com/#/detail/1587450584
Document information
Published on 01/01/2007
Volume 2007, 2007
DOI: 10.1007/978-3-540-71617-4_18
Licence: CC BY-NC-SA license
Share this document
Keywords
claim authorship
Are you one of the authors of this document?