RFC 5690 on Adding Acknowledgement Congestion Control to TCP

rfc-editor@rfc-editor.org Thu, 04 February 2010 01:46 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 8805628C113 for <ietf-announce@core3.amsl.com>; Wed, 3 Feb 2010 17:46:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id H4mNYmdENVdu for <ietf-announce@core3.amsl.com>; Wed, 3 Feb 2010 17:46:56 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id A287D28C112 for <ietf-announce@ietf.org>; Wed, 3 Feb 2010 17:46:56 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 512C2130008; Wed, 3 Feb 2010 17:47:41 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5690 on Adding Acknowledgement Congestion Control to TCP
From: rfc-editor@rfc-editor.org
Message-Id: <20100204014741.512C2130008@rfc-editor.org>
Date: Wed, 3 Feb 2010 17:47:41 -0800 (PST)
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2010 01:46:57 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 5690

        Title:      Adding Acknowledgement Congestion Control to 
        Author:     S. Floyd, A. Arcia,
                    D. Ros, J. Iyengar
        Status:     Informational
        Date:       February 2010
        Mailbox:    floyd@icir.org, 
                    David.Ros@telecom-bretagne.eu,  jiyengar@fandm.edu
        Pages:      33
        Characters: 83437
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-floyd-tcpm-ackcc-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5690.txt

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.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC