Re: [tsvwg] [Technical Errata Reported] RFC3390 (4569)
Mitchell Erblich <erblichs@earthlink.net> Mon, 04 January 2016 20:35 UTC
Return-Path: <erblichs@earthlink.net>
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 DA3541A9238 for <tsvwg@ietfa.amsl.com>; Mon, 4 Jan 2016 12:35:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level:
X-Spam-Status: No, score=-2.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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 z50ls2U44C-3 for <tsvwg@ietfa.amsl.com>; Mon, 4 Jan 2016 12:35:04 -0800 (PST)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by ietfa.amsl.com (Postfix) with ESMTP id BF3871A9173 for <tsvwg@ietf.org>; Mon, 4 Jan 2016 12:35:04 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=YKJxDKKGXsepBdHhkBoQAYa8K5IrFrpy32IM2J+M9HZGLaaXwcnY49AvRrReynBM; h=Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Received: from [50.136.188.174] (helo=[10.0.0.5]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <erblichs@earthlink.net>) id 1aGBpV-0003bh-Ro; Mon, 04 Jan 2016 15:34:14 -0500
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Mitchell Erblich <erblichs@earthlink.net>
In-Reply-To: <31029.1451936958@lawyers.icir.org>
Date: Mon, 04 Jan 2016 12:34:09 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <DBDB4A19-1DC7-46A1-8B61-C1B98C9B8AD7@earthlink.net>
References: <31029.1451936958@lawyers.icir.org>
To: mallman@icir.org
X-Mailer: Apple Mail (2.1878.6)
X-ELNK-Trace: 074f60c55517ea841aa676d7e74259b7b3291a7d08dfec79fc98516f39f944b318cba6503fa21f8c350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 50.136.188.174
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/KX7E1XqJjLleu8vN2X12eK4ymCo>
Cc: gorry@erg.abdn.ac.uk, floyd@icir.org, nmalykh@gmail.com, craig@bbn.com, mls.ietf@gmail.com, tsvwg@ietf.org, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [tsvwg] [Technical Errata Reported] RFC3390 (4569)
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: Mon, 04 Jan 2016 20:35:07 -0000
Mark Allman and group, As a later follow-up…. Wouldn’t it make sense to mention that TCP’s Reno’s Fast Re-transmit” capability suggests that initial increases of the initial window should generate earlier detection of congestion because of the non-wait of the coarse timeout ,, assuming that the number of Dup ACKs is adjusted accordingly? Mitchell Erblich On Jan 4, 2016, at 11:49 AM, Mark Allman <mallman@icir.org> wrote: > > Yep- this is a small error that could well be noted in the RFC > errata. > > I looked at it has its roots in RFC 2414 (the RFC that 3390 > obsoleted). So, you might as well add a note to that one, too. > > 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=4569 >> >> -------------------------------------- >> Type: Technical >> Reported by: Nikolai Malykh <nmalykh@gmail.com> >> >> Section: 8.1 >> >> Original Text >> ------------- >> A second set of experiments explored TCP performance over dialup >> modem links. In experiments over a 28.8 bps dialup channel [All97a, >> AHO98], a four-segment initial window decreased the transfer time of >> a 16KB file by roughly 10%, with no accompanying increase in the drop >> rate. A simulation study [RFC2416] investigated the effects of using >> a larger initial window on a host connected by a slow modem link and >> a router with a 3 packet buffer. The study concluded that for the >> scenario investigated, the use of larger initial windows was not >> harmful to TCP performance. >> >> Corrected Text >> -------------- >> A second set of experiments explored TCP performance over dialup >> modem links. In experiments over a 28.8 Kbps dialup channel [All97a, >> AHO98], a four-segment initial window decreased the transfer time of >> a 16KB file by roughly 10%, with no accompanying increase in the drop >> rate. A simulation study [RFC2416] investigated the effects of using >> a larger initial window on a host connected by a slow modem link and >> a router with a 3 packet buffer. The study concluded that for the >> scenario investigated, the use of larger initial windows was not >> harmful to TCP performance. >> >> Notes >> ----- >> Error bit rate - bps instead of Kbps. >> >> 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 > > > >
- [tsvwg] [Technical Errata Reported] RFC3390 (4569) RFC Errata System
- Re: [tsvwg] [Technical Errata Reported] RFC3390 (… lloyd.wood
- Re: [tsvwg] [Technical Errata Reported] RFC3390 (… Mark Allman
- Re: [tsvwg] [Technical Errata Reported] RFC3390 (… Mitchell Erblich
- Re: [tsvwg] [Technical Errata Reported] RFC3390 (… Mark Allman
- Re: [tsvwg] [Technical Errata Reported] RFC3390 (… Megan Ferguson
- Re: [tsvwg] [Technical Errata Reported] RFC3390 (… Craig Partridge
- Re: [tsvwg] [Technical Errata Reported] RFC3390 (… lloyd.wood
- Re: [tsvwg] [Technical Errata Reported] RFC3390 (… Joe Touch
- Re: [tsvwg] [Technical Errata Reported] RFC3390 (… Joe Touch
- [tsvwg] [Errata Verified] RFC3390 (4569) RFC Errata System