Adding Acknowledgement Congestion Control to TCP
RFC 5690, “Adding Acknowledgement Congestion Control to TCP”, is an Informational document published in February 2010 by S. Floyd, A. Arcia, D. Ros, J. Iyengar. The canonical text is published by the RFC Editor.
Abstract
This document describes a possible congestion control mechanism for acknowledgement (ACKs) traffic in TCP. The document specifies an end-to-end acknowledgement congestion control mechanism for TCP that uses participation from both TCP hosts: the TCP data sender and the TCP data receiver. The TCP data sender detects lost or Explicit Congestion Notification (ECN)-marked ACK packets, and tells the TCP data receiver the ACK Ratio R to use to respond to the congestion on the reverse path from the data receiver to the data sender. The TCP data receiver sends roughly one ACK packet for every R data packets received. This mechanism is based on the acknowledgement congestion control in the Datagram Congestion Control Protocol's (DCCP's) Congestion Control Identifier (CCID) 2. This acknowledgement congestion control mechanism is being specified for further evaluation by the network community. This document is not an Internet Standards Track specification; it is published for informational purposes.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 5690 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5688 A Session Initiation Protocol Media Feature Tag for MIME Application Subtypes
- RFC 5687 GEOPRIV Layer 7 Location Configuration Protocol: Problem Statement and Requirements
- RFC 5684 Unintended Consequences of NAT Deployments with Overlapping Address Space
- RFC 5683 Password-Authenticated Key Diffie-Hellman Exchange
- RFC 5705 Keying Material Exporters for Transport Layer Security
- RFC 5707 Media Server Markup Language
- RFC 5708 X.509 Key and Signature Encoding for the KeyNote Trust Management System
- RFC 5710 PathErr Message Triggered MPLS and GMPLS LSP Reroutes