[tcpm] RFC 6928 on Increasing TCP's Initial Window

rfc-editor@rfc-editor.org Mon, 29 April 2013 18:51 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAF4F21F8529; Mon, 29 Apr 2013 11:51:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level:
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tGjibCXXQ77m; Mon, 29 Apr 2013 11:51:45 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id BA74421F9804; Mon, 29 Apr 2013 11:51:24 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4D80CB1E015; Mon, 29 Apr 2013 11:50:59 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130429185059.4D80CB1E015@rfc-editor.org>
Date: Mon, 29 Apr 2013 11:50:59 -0700
Cc: tcpm@ietf.org, rfc-editor@rfc-editor.org
Subject: [tcpm] RFC 6928 on Increasing TCP's Initial Window
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 18:51:47 -0000

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

        
        RFC 6928

        Title:      Increasing TCP's Initial Window 
        Author:     J. Chu, N. Dukkipati,
                    Y. Cheng, M. Mathis
        Status:     Experimental
        Stream:     IETF
        Date:       April 2013
        Mailbox:    hkchu@google.com, 
                    nanditad@google.com, 
                    ycheng@google.com,
                    mattmathis@google.com
        Pages:      24
        Characters: 56523
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tcpm-initcwnd-08.txt

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

This document proposes an experiment to increase the permitted TCP
initial window (IW) from between 2 and 4 segments, as specified in
RFC 3390, to 10 segments with a fallback to the existing
recommendation when performance issues are detected.  It discusses the
motivation behind the increase, the advantages and disadvantages of
the higher initial window, and presents results from several large-scale
experiments showing that the higher initial window improves the
overall performance of many web services without resulting in a
congestion collapse.  The document closes with a discussion of usage
and deployment for further experimental purposes recommended by the
IETF TCP Maintenance and Minor Extensions (TCPM) working group.

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


EXPERIMENTAL: 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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