TCP Congestion Control with Appropriate Byte Counting (ABC)
draft-allman-tcp-abc-04

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3465.
Author Mark Allman
Last updated 2015-10-14 (Latest revision 2002-11-04)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Experimental
Formats
txt htmlized pdf bibtex bibxml
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3465 (Experimental)
Action Holders
(None)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Allison J. Mankin
IESG note
Send notices to (None)
Email authors IPR References Referenced by Nits Search email archive
draft-allman-tcp-abc-04 
A new Request for Comments is now available in online RFC libraries.

        RFC 3465

        Title:      TCP Congestion Control with Appropriate Byte
                    Counting (ABC)
        Author(s):  M. Allman
        Status:     Experimental
        Date:       February 2003
        Mailbox:    mallman@bbn.com
        Pages:      10
        Characters: 23486
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-allman-tcp-abc-04.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3465.txt

This document proposes a small modification to the way TCP increases
its congestion window.  Rather than the traditional method of
increasing the congestion window by a constant amount for each
arriving acknowledgment, the document suggests basing the increase
on the number of previously unacknowledged bytes each ACK covers.
This change improves the performance of TCP, as well as closes a
security hole TCP receivers can use to induce the sender into
increasing the sending rate too rapidly.

This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind.  Discussion and
suggestions for improvement are requested.  Distribution of this memo
is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.