RFC 6582 on The NewReno Modification to TCP's Fast Recovery Algorithm

rfc-editor@rfc-editor.org Fri, 06 April 2012 21:13 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 6E95E11E80CC; Fri, 6 Apr 2012 14:13:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.841
X-Spam-Status: No, score=-103.841 tagged_above=-999 required=5 tests=[AWL=1.236, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id QB0sr8Gfxemq; Fri, 6 Apr 2012 14:13:29 -0700 (PDT)
Received: from rfc-editor.org (rfcpa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 72B6F11E80DC; Fri, 6 Apr 2012 14:13:29 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id DA357B1E018; Fri, 6 Apr 2012 14:13:10 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6582 on The NewReno Modification to TCP's Fast Recovery Algorithm
From: rfc-editor@rfc-editor.org
Message-Id: <20120406211310.DA357B1E018@rfc-editor.org>
Date: Fri, 06 Apr 2012 14:13:10 -0700
Cc: tcpm@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 06 Apr 2012 21:13:30 -0000

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

        RFC 6582

        Title:      The NewReno Modification to TCP's 
                    Fast Recovery Algorithm 
        Author:     T. Henderson, S. Floyd,
                    A. Gurtov, Y. Nishida
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2012
        Mailbox:    thomas.r.henderson@boeing.com, 
        Pages:      16
        Characters: 35413
        Obsoletes:  RFC3782

        I-D Tag:    draft-ietf-tcpm-rfc3782-bis-05.txt

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

RFC 5681 documents the following four intertwined TCP
congestion control algorithms: slow start, congestion avoidance, fast
retransmit, and fast recovery.  RFC 5681 explicitly allows
certain modifications of these algorithms, including modifications
that use the TCP Selective Acknowledgment (SACK) option (RFC 2883),
and modifications that respond to "partial acknowledgments" (ACKs
that cover new data, but not all the data outstanding when loss was
detected) in the absence of SACK.  This document describes a specific
algorithm for responding to partial acknowledgments, referred to as
"NewReno".  This response to partial acknowledgments was first proposed
by Janey Hoe.  This document obsoletes RFC 3782.  [STANDARDS-TRACK]

This document is a product of the TCP Maintenance and Minor Extensions Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  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