Re: [tcpm] Request for input regarding the initial window increase

Wesley Eddy <wes@mti-systems.com> Wed, 13 July 2011 00:53 UTC

Return-Path: <wes@mti-systems.com>
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 C86EF11E80D3 for <tcpm@ietfa.amsl.com>; Tue, 12 Jul 2011 17:53:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ybuilTVCQm-w for <tcpm@ietfa.amsl.com>; Tue, 12 Jul 2011 17:53:01 -0700 (PDT)
Received: from omr7.networksolutionsemail.com (omr7.networksolutionsemail.com [205.178.146.57]) by ietfa.amsl.com (Postfix) with ESMTP id 2ACF411E80C7 for <tcpm@ietf.org>; Tue, 12 Jul 2011 17:53:00 -0700 (PDT)
Received: from cm-omr3 (mail.networksolutionsemail.com [205.178.146.50]) by omr7.networksolutionsemail.com (8.13.6/8.13.6) with ESMTP id p6D0r0rK003463 for <tcpm@ietf.org>; Tue, 12 Jul 2011 20:53:00 -0400
Authentication-Results: cm-omr3 smtp.user=wes@mti-systems.com; auth=pass (PLAIN)
X-Authenticated-UID: wes@mti-systems.com
Received: from [174.130.71.64] ([174.130.71.64:4514] helo=[192.168.1.103]) by cm-omr3 (envelope-from <wes@mti-systems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 82/4D-28066-C6CEC1E4; Tue, 12 Jul 2011 20:53:00 -0400
Message-ID: <4E1CEC6C.7030607@mti-systems.com>
Date: Tue, 12 Jul 2011 20:53:00 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: tcpm@ietf.org
References: <133D9897FB9C5E4E9DF2779DC91E947C0654B57A@SLFSNX.rcs.alcatel-research.de>
In-Reply-To: <133D9897FB9C5E4E9DF2779DC91E947C0654B57A@SLFSNX.rcs.alcatel-research.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [tcpm] Request for input regarding the initial window increase
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: Wed, 13 Jul 2011 00:53:01 -0000

My personal responses as a WG participant are below:

On 7/12/2011 7:54 PM, SCHARF, Michael wrote:
>
> ...
>
> Question 1: Moving forward a fixed increase of the permitted TCP initial
> congestion window (draft-ietf-tcpm-initcwnd-01)?
>
> Answer 1A: Fixed upper limit to proposed standard
> Answer 2B: Fixed upper limit to experimental
> Answer 3C: Something else (e. g., some adaptive scheme, or no change at
> all compared to RFC 3390); this would imply a substantial change of
> draft-ietf-tcpm-initcwnd-01

I think B (Experimental) is a conservative approach.  I'm happy with
that and scoping the "experiment" for general use on the Internet, with
intent to come back and go to Proposed Standard at some point.
Essentially, it already has close to that status ;).


> Question 2: Maximum permitted initial congestion window?
>
> Answer 2A: 10 MSS for an MTU of 1500 byte as suggested by
> draft-ietf-tcpm-initcwnd-01 (other MTUs are still TBD)
> Answer 2B: Another value (please suggest and justify)

I think 2A is appropriate due to the volume of analysis that used the
same value (10MSS).  Anything greater hasn't been looked at as much,
and anything lesser sacrifices the intent.


> Question 3: Adaptive solution as an alternative?
>
> Answer 3A: Adoption of draft-touch-tcpm-automatic-iw-01 as WG item
> heading towards experimental
> Answer 3B: No adoption


I favor 3A, sort-of.  I would rather see it generalized to explain how 
the same algorithm can be used for tuning SCTP and potentially a subset 
of CCIDs for DCCP.  Otherwise we're begging someone to write more
documents later in order to tell us how the same thing applies to those
other protocols.

-- 
Wes Eddy
MTI Systems