Improving the Robustness of TCP to Non-Congestion Events
RFC 4653, “Improving the Robustness of TCP to Non-Congestion Events”, is an Experimental document published in August 2006 by S. Bhandarkar, A. L. N. Reddy, M. Allman, E. Blanton. The canonical text is published by the RFC Editor.
Abstract
This document specifies Non-Congestion Robustness (NCR) for TCP. In the absence of explicit congestion notification from the network, TCP uses loss as an indication of congestion. One of the ways TCP detects loss is using the arrival of three duplicate acknowledgments. However, this heuristic is not always correct, notably in the case when network paths reorder segments (for whatever reason), resulting in degraded performance. TCP-NCR is designed to mitigate this degraded performance by increasing the number of duplicate acknowledgments required to trigger loss recovery, based on the current state of the connection, in an effort to better disambiguate true segment loss from segment reordering. This document specifies the changes to TCP, as well as the costs and benefits of these modifications. This memo defines an Experimental Protocol for the Internet community.
What “Experimental” means
Describes a specification that is part of a research or development effort, published so the community can gain experience with it.
The canonical text of RFC 4653 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4652 Evaluation of Existing Routing Protocols against Automatic Switched Optical Network Routing Requirements
- RFC 4654 TCP-Friendly Multicast Congestion Control : Protocol Specification
- RFC 4655 A Path Computation Element -Based Architecture
- RFC 4650 HMAC-Authenticated Diffie-Hellman for Multimedia Internet KEYing
- RFC 4656 A One-way Active Measurement Protocol
- RFC 4649 Dynamic Host Configuration Protocol for IPv6 Relay Agent Remote-ID Option
- RFC 4657 Path Computation Element Communication Protocol Generic Requirements
- RFC 4648 The Base16, Base32, and Base64 Data Encodings