J. Nagle, RFC 896: Congestion Control in IP/TCP Internetworks, January 1984. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Robust TCP Connections for Fault Tolerant Computing - Ekwall, Urbán, Schiper (2002) (1 citation) (Correct)
....is full. Let us contrast this implementation to the in band solution. The problems are the following: Multiplexing and demultiplexing two streams may be costly by itself, especially if data is transmitted in small chunks. This is the easiest problem: a solution similar to Nagle s algorithm [5] could offer acceptable performance. The data stream and the stream of control messages are independent: even if no data is sent to one of the communication parties, that party may still receive control messages. For this reason, each party has to constantly read the TCP stream to check for ....
J. Nagle. RFC 896: Congestion control in IP/TCP internetworks, Jan. 1984. Status: UNKNOWN.
Probing TCP Implementations - Comer, Lin (1994) (24 citations) (Correct)
....and reorder packets) The ability of TCP to adapt to networks of various characteristics and computer systems of various processing power makes TCP an important component in the fast expansion of the global Internet. The original definition of TCP appears in RFC 793 [14] Many researchers [2, 7, 8, 9, 11, 12, 18, 19] have identified problems and weakness of the protocol, and proposed solutions. RFC 1122 [1] updates and supplements the definition; to meet the TCP standard, an implementation must follow both RFC 793 and RFC1122. This workwas supported in part by a fellowship from UniForum. Although RFCs 793 and ....
....hand, if the sender uses a smaller RTO value than the actual packet round trip time (RTT) unnecessary retransmissions occur. Moreover, if the packet round triptime increase is due to network congestion, unnecessary retransmissions make the situation even worse and may lead to congestion collapse [12]. On the other hand, if the sender uses a larger RTO value, a lost packet causes the sender to wait longer than necessary, thus degrading throughput. The calculation of the RTO value originally suggested in RFC 793 is now known to be inadequate and has been replaced. RFC 1122 specifies the new ....
John Nagle. RFC-896: Congestion Control in IP/TCP Internetworks. Request For Comments, January 1984. Network Information Center.
HG-RCP: A Rate-Based Traffic Management Mechanism for.. - Hassan, Breen (1997) (Correct)
No context found.
J. Nagle, RFC 896: Congestion Control in IP/TCP Internetworks, January 1984.
Network Capacity Sharing with QoS as a Financial Derivative.. - Rasmusson (2002) (Correct)
No context found.
John Nagle. RFC 896: Congestion Control in IP/TCP Internetwork. IETF, January 1984.
Multi-Layer Network Monitoring and Analysis - Hall (2003) (2 citations) (Correct)
No context found.
J. Nagle. RFC 896: Congestion control in IP/TCP internetworks, January 1984. Status: INFORMATIONAL. (pp 114, 120, 161)
Opportunistic Use of Content Addressable Storage.. - Tolia, Kozuch.. (2003) (4 citations) (Correct)
No context found.
NAGLE, J. RFC 896: Congestion Control in IP/TCP Internetworks (January 1984).
A Neural Network Algorithm for Internetwork Routing - Will Newton Wrn (Correct)
No context found.
John Nagle. RFC 896: Congestion Control in IP/TCP Internetworks. Technical report, Internet Engineering Task Force, 1984.
Tool-Based Specialization of Protocol Stacks in.. - Bhatia, Consel, Le.. (Correct)
No context found.
J. Nagle. RFC 896: Congestion control in IP/TCP internetworks, January 1984. Status: UNKNOWN.
Opportunistic Use of Content Addressable Storage.. - Tolia, Kozuch.. (2003) (4 citations) (Correct)
No context found.
NAGLE, J. RFC 896: Congestion Control in IP/TCP Internetworks (January 1984).
Opportunistic Use of Content Addressable Storage.. - Tolia, Kozuch.. (2003) (4 citations) (Correct)
No context found.
NAGLE, J. RFC 896: Congestion Control in IP/TCP Internetworks (January 1984).
Non-Intrusive Estimation of Web Server Delays - Hall, Pratt, Leslie (2001) (2 citations) (Correct)
No context found.
J. Nagle. RFC 896: Congestion control in IP/TCP internetworks, Jan. 1984.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC