Re: [tsvwg] [Technical Errata Reported] RFC3390 (4583)

Joe Touch <touch@isi.edu> Wed, 06 January 2016 19:20 UTC

Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA89E1A0126 for <tsvwg@ietfa.amsl.com>; Wed, 6 Jan 2016 11:20:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jEW8TVtCWJbM for <tsvwg@ietfa.amsl.com>; Wed, 6 Jan 2016 11:20:30 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 809D11A011D for <tsvwg@ietf.org>; Wed, 6 Jan 2016 11:20:30 -0800 (PST)
Received: from [128.9.160.211] (mul.isi.edu [128.9.160.211]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id u06JJAcF012152 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 6 Jan 2016 11:19:12 -0800 (PST)
To: mallman@icir.org, RFC Errata System <rfc-editor@rfc-editor.org>
References: <15654.1452107372@lawyers.icir.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <568D68AE.5040407@isi.edu>
Date: Wed, 06 Jan 2016 11:19:10 -0800
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <15654.1452107372@lawyers.icir.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/rtMR2gLDPuQ27CeCRUup_OQXjRA>
Cc: gorry@erg.abdn.ac.uk, floyd@icir.org, touch@isi.edu, craig@bbn.com, mls.ietf@gmail.com, tsvwg@ietf.org
Subject: Re: [tsvwg] [Technical Errata Reported] RFC3390 (4583)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2016 19:20:33 -0000


On 1/6/2016 11:09 AM, Mark Allman wrote:
> 
> This is clearly a correction to the document.  The intent of the
> authors and the WG was never to allow the initial window to be
> higher than given in the document.  (It was hard enough to get folks
> to accept an initial window of 2-4 segments.  It'd have been
> impossible to get the community to agree to leave an explicit escape
> hatch for larger values.)
> 
> This error also applies to RFC 2414 (where the text originated).

Agreed, but since 2414 is obsoleted by 3390, do we also need an errata
there too?

Joe


> 
> allman
> 
> 
> 
>> The following errata report has been submitted for RFC3390,
>> "Increasing TCP's Initial Window".
>>
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=3390&eid=4583
>>
>> --------------------------------------
>> Type: Technical
>> Reported by: Joe Touch <touch@isi.edu>
>>
>> Section: 1.
>>
>> Original Text
>> -------------
>>    This increased initial window is optional: a TCP MAY start with a
>>    larger initial window.  However, we expect that most general-purpose
>>    TCP implementations would choose to use the larger initial congestion
>>    window given in equation (1) above.
>>
>> Corrected Text
>> --------------
>>    This increased initial window is optional: a TCP MAY start with a
>>    smaller initial window.  However, we expect that most general-purpose
>>    TCP implementations would choose to use the larger initial congestion
>>    window given in equation (1) above.
>>
>> Notes
>> -----
>> The MAY allows use of values smaller than this document allows, not larger.
>>
>> Instructions:
>> -------------
>> This erratum is currently posted as "Reported". If necessary, please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party (IESG)
>> can log in to change the status and edit the report, if necessary. 
>>
>> --------------------------------------
>> RFC3390 (draft-ietf-tsvwg-initwin-04)
>> --------------------------------------
>> Title: Increasing TCP's Initial Window
>> Publication Date    : October 2002
>> Author(s): M. Allman, S. Floyd, C. Partridge
>> Category: PROPOSED STANDARD
>> Source: Transport Area Working Group
>> Area: Transport
>> Stream: IETF
>> Verifying Party     : IESG
> 
> 
> 
>