public:wan_optimization
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
public:wan_optimization [2020/05/04 11:44] – created lstolp | public:wan_optimization [2024/01/25 03:31] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | RFC 1323 Window Scaling & Timestamps | + | {{public: |
- | RFC 2018 Selective ACK | + | This memo presents a set of TCP extensions to improve performance |
- | RFC 2001/ | + | over large bandwidth*delay product paths and to provide reliable |
- | RFC 2414/3390 Increase initial window size | + | operation over very high-speed paths. |
- | RFC 2873 Accept TOS/ | + | scaled windows and timestamps, which are designed to provide |
- | RFC 2988 RTO calculation | + | compatible interworking with TCP’s that do not implement the |
- | RFC 3042 Limited transmit | + | extensions. |
- | RFC 3465 ABC | + | RTTM (Round Trip Time Measurement) and PAWS (Protect Against Wrapped |
- | RFC 3517 SACK sender behavior | + | Sequences). |
- | RFC 3649 High Speed TCP | + | |
+ | {{public: | ||
+ | TCP may experience poor performance when multiple packets are lost | ||
+ | from one window of data. With the limited information available | ||
+ | from cumulative acknowledgments, | ||
+ | | ||
+ | | ||
+ | may have already been successfully received. | ||
+ | A Selective Acknowledgment (SACK) mechanism, combined with a | ||
+ | | ||
+ | | ||
+ | | ||
+ | then retransmit only the missing data segments. | ||
+ | |||
+ | {{public: | ||
+ | | ||
+ | that have never been fully documented as Internet standards: | ||
+ | | ||
+ | and [3] provide some details on these algorithms, [4] provides | ||
+ | | ||
+ | code for the 4.4BSD implementation. | ||
+ | must implement slow start and congestion avoidance (Section 4.2.2.15 | ||
+ | of [1]), citing [2] as the reference, but fast retransmit and fast | ||
+ | | ||
+ | | ||
+ | |||
+ | {{public: | ||
+ | This document specifies an optional standard for TCP to increase the | ||
+ | | ||
+ | | ||
+ | | ||
+ | of experiments and simulations showing that the higher initial window | ||
+ | does not lead to congestion collapse. | ||
+ | | ||
+ | |||
+ | {{public: | ||
+ | This memo describes a conflict between TCP [RFC793] and DiffServ | ||
+ | | ||
+ | an IPv4 header [RFC791]. In a network that contains DiffServ-capable | ||
+ | | ||
+ | | ||
+ | | ||
+ | the conflict. | ||
+ | | ||
+ | | ||
+ | does not define precedence or security parameter bits, there is no | ||
+ | | ||
+ | | ||
+ | |||
+ | {{public: | ||
+ | This document defines the standard algorithm that Transmission | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | {{public: | ||
+ | This document proposes a new Transmission Control Protocol (TCP) | ||
+ | | ||
+ | when a connection’s congestion window is small, or when a large | ||
+ | | ||
+ | " | ||
+ | | ||
+ | | ||
+ | | ||
+ | fast retransmit algorithm, rather than using a costly retransmission | ||
+ | | ||
+ | in the absence of, the TCP selective acknowledgment (SACK) mechanism. | ||
+ | |||
+ | {{public: | ||
+ | This document proposes a small modification to the way TCP increases | ||
+ | its congestion window. | ||
+ | | ||
+ | | ||
+ | the number of previously unacknowledged bytes each ACK covers. | ||
+ | | ||
+ | hole TCP receivers can use to induce the sender into increasing the | ||
+ | | ||
+ | |||
+ | {{public: | ||
+ | This document presents a conservative loss recovery algorithm for TCP | ||
+ | that is based on the use of the selective acknowledgment (SACK) TCP | ||
+ | | ||
+ | | ||
+ | but allows TCP senders to recover more effectively when multiple | ||
+ | | ||
+ | |||
+ | {{public: | ||
+ | The proposals in this document are experimental. | ||
+ | | ||
+ | that this is the best method for high-speed congestion control. | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | This document proposes HighSpeed TCP, a modification to TCP’s | ||
+ | | ||
+ | | ||
+ | | ||
+ | by TCP in realistic environments. | ||
+ | | ||
+ | | ||
+ | | ||
+ | of at most one congestion event every 5, | ||
+ | | ||
+ | is widely acknowledged as an unrealistic constraint. | ||
+ | | ||
+ | | ||
public/wan_optimization.1588592656.txt.gz · Last modified: 2024/01/25 03:32 (external edit)